Sirvoy Status - Incident history https://status.sirvoy.com Sirvoy Wed, 3 Jun 2026 02:00:00 +0000 Airbnb Availability/Prices Updates Outage Type: Incident Duration: 2 days, 1 hour and 11 minutes Affected Components: Airbnb Jun 3, 02:00:00 GMT+0 - Identified - Airbnb is experiencing an outage involving the retrieval of Sirvoy availability and price updates, they are not being accepted by Airbnb. There could be a resulting temporary discrepancy in availability and prices while this outage lasts. All pending updates will be retried, so no action is needed on your part. Jun 5, 03:11:00 GMT+0 - Resolved - Airbnb experienced an outage that has been solved now. The outage involved Airbnb not accepting Sirvoy updates of availability and prices. There could have been a temporary discrepancy of availability if you received bookings during this outage period. Airbnb fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part. Type: Incident

Duration: 2 days, 1 hour and 11 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br><strong>Identified</strong> - Airbnb is experiencing an outage involving the retrieval of Sirvoy availability and price updates, they are not being accepted by Airbnb. There could be a resulting temporary discrepancy in availability and prices while this outage lasts. All pending updates will be retried, so no action is needed on your part..</p> <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>03:11:00</var> GMT+0</small><br><strong>Resolved</strong> - Airbnb experienced an outage that has been solved now. The outage involved Airbnb not accepting Sirvoy updates of availability and prices. There could have been a temporary discrepancy of availability if you received bookings during this outage period. Airbnb fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part..</p> ]]> Wed, 3 Jun 2026 02:00:00 +0000 https://status.sirvoy.com/incident/cmq06g4ms05jnnwyma0w2hy82 https://status.sirvoy.com/incident/cmq06g4ms05jnnwyma0w2hy82 SMS delivery status may incorrectly show as pending Type: Incident Duration: 5 hours and 28 minutes Affected Components: SMS May 26, 09:00:00 GMT+0 - Identified - We are investigating an issue where SMS delivery statuses in Sirvoy may incorrectly show as **pending**, even when the SMS has been delivered. SMS delivery itself is **not expected to be affected**, but the displayed status may be incorrect. May 26, 14:28:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 26, 14:28:01 GMT+0 - Resolved - This incident has been resolved. SMS messages sent after the fix will show the correct delivery status. SMS messages sent before the fix may still show as “Pending,” even if they were successfully delivered to the recipient. Type: Incident

Duration: 5 hours and 28 minutes

Affected Components:

<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are investigating an issue where SMS delivery statuses in Sirvoy may incorrectly show as **pending**, even when the SMS has been delivered. SMS delivery itself is **not expected to be affected**, but the displayed status may be incorrect..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>14:28:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>14:28:01</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. SMS messages sent after the fix will show the correct delivery status. SMS messages sent before the fix may still show as “Pending,” even if they were successfully delivered to the recipient..</p> ]]> Tue, 26 May 2026 09:00:00 +0000 https://status.sirvoy.com/incident/cmpo1mzcg01xup4ltaz5tmeq6 https://status.sirvoy.com/incident/cmpo1mzcg01xup4ltaz5tmeq6 Expedia Outage Type: Incident Duration: 3 hours and 16 minutes Affected Components: Expedia May 24, 19:30:00 GMT+0 - Resolved - The Expedia outage has now been resolved. The issue affected both the retrieval of bookings into Sirvoy and Expedia’s acceptance of availability and price updates. **Booking retrieval:** Bookings made on Expedia during the outage will automatically import to Sirvoy over time. Please verify a few hours after the outage has ended that all bookings were imported successfully. Expedia offers fallback solutions for receiving bookings, modifications, and cancellations by email during outages. **Availability and prices:** Expedia has fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part. If you received bookings during the outage period, there could have been a temporary discrepancy of availability. May 24, 07:38:00 GMT+0 - Identified - Expedia is experiencing an outage that has not yet been resolved. This is affecting both the retrieval of bookings into Sirvoy and Expedia’s acceptance of Sirvoy availability and price updates. **Booking retrieval (Expedia → Sirvoy):** During the outage, bookings and updates made in Expedia are not sent to Sirvoy. After the outage is resolved, Expedia will send any missing bookings and updates to Sirvoy over time. Expedia offers fallback solutions for receiving bookings, modifications, and cancellations by email during outages. **Availability and price updates (Sirvoy → Expedia):** Availability and price updates are not being accepted by Expedia. This may result in a temporary discrepancy in availability and prices while the outage lasts. All pending updates will be retried, so no action is needed on your part. There will be an update here when the outage resolves. Type: Incident

Duration: 3 hours and 16 minutes

Affected Components:

<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>19:30:00</var> GMT+0</small><br><strong>Resolved</strong> - The Expedia outage has now been resolved. The issue affected both the retrieval of bookings into Sirvoy and Expedia’s acceptance of availability and price updates. **Booking retrieval:** Bookings made on Expedia during the outage will automatically import to Sirvoy over time. Please verify a few hours after the outage has ended that all bookings were imported successfully. Expedia offers fallback solutions for receiving bookings, modifications, and cancellations by email during outages. **Availability and prices:** Expedia has fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part. If you received bookings during the outage period, there could have been a temporary discrepancy of availability. .</p> <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>07:38:00</var> GMT+0</small><br><strong>Identified</strong> - Expedia is experiencing an outage that has not yet been resolved. This is affecting both the retrieval of bookings into Sirvoy and Expedia’s acceptance of Sirvoy availability and price updates. **Booking retrieval (Expedia → Sirvoy):** During the outage, bookings and updates made in Expedia are not sent to Sirvoy. After the outage is resolved, Expedia will send any missing bookings and updates to Sirvoy over time. Expedia offers fallback solutions for receiving bookings, modifications, and cancellations by email during outages. **Availability and price updates (Sirvoy → Expedia):** Availability and price updates are not being accepted by Expedia. This may result in a temporary discrepancy in availability and prices while the outage lasts. All pending updates will be retried, so no action is needed on your part. There will be an update here when the outage resolves..</p> ]]> Sun, 24 May 2026 07:38:00 +0000 https://status.sirvoy.com/incident/cmpk045q10fk3pbi0soz2zl8s https://status.sirvoy.com/incident/cmpk045q10fk3pbi0soz2zl8s Booking.com Booking Retrieval Outage Type: Incident Duration: 3 hours and 54 minutes Affected Components: Booking.com May 21, 14:29:00 GMT+0 - Resolved - The Booking.com outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 36h. If you seem to have bookings from Booking.com that don't appear in Sirvoy even after 36h then please email us at [support@sirvoy.com](mailto:support@sirvoy.com) to let us know and include your username in the email. Any cancellations made during the outage will not be automatically retrieved. If you did receive cancellations, please email us the reservation number and we will be able to update the booking to its cancelled status. May 21, 10:35:00 GMT+0 - Identified - Booking.com is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Booking.com will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Booking.com if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves. Type: Incident

Duration: 3 hours and 54 minutes

Affected Components:

<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>14:29:00</var> GMT+0</small><br><strong>Resolved</strong> - The Booking.com outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 36h. If you seem to have bookings from Booking.com that don't appear in Sirvoy even after 36h then please email us at [support@sirvoy.com](mailto:support@sirvoy.com) to let us know and include your username in the email. Any cancellations made during the outage will not be automatically retrieved. If you did receive cancellations, please email us the reservation number and we will be able to update the booking to its cancelled status..</p> <p><small>May <var data-var='date'> 21</var>, <var data-var='time'>10:35:00</var> GMT+0</small><br><strong>Identified</strong> - Booking.com is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Booking.com will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Booking.com if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves..</p> ]]> Thu, 21 May 2026 10:35:00 +0000 https://status.sirvoy.com/incident/cmpfd60gs092vp9xar3bsdizc https://status.sirvoy.com/incident/cmpfd60gs092vp9xar3bsdizc Airbnb Booking Retrieval Outage Type: Incident Duration: 4 hours and 2 minutes Affected Components: Airbnb May 19, 06:32:00 GMT+0 - Resolved - The Airbnb outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 24h. If you seem to have bookings from Airbnb that don't appear in Sirvoy even after 24h you have the option to import these into Sirvoy. Please go to Settings -> Channels -> Airbnb and click “Edit” to check the import tool. Any cancellations made during the outage will not be automatically retrieved. If you did receive cancellations, please email us the reservation number and we will be able to update the booking to its cancelled status. May 19, 02:30:00 GMT+0 - Identified - Airbnb is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Airbnb will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. Type: Incident

Duration: 4 hours and 2 minutes

Affected Components:

<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>06:32:00</var> GMT+0</small><br><strong>Resolved</strong> - The Airbnb outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 24h. If you seem to have bookings from Airbnb that don't appear in Sirvoy even after 24h you have the option to import these into Sirvoy. Please go to Settings -> Channels -> Airbnb and click “Edit” to check the import tool. Any cancellations made during the outage will not be automatically retrieved. If you did receive cancellations, please email us the reservation number and we will be able to update the booking to its cancelled status..</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>02:30:00</var> GMT+0</small><br><strong>Identified</strong> - Airbnb is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Airbnb will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings..</p> ]]> Tue, 19 May 2026 02:30:00 +0000 https://status.sirvoy.com/incident/cmpccxdgd03a0qpqs0q9w7p1a https://status.sirvoy.com/incident/cmpccxdgd03a0qpqs0q9w7p1a Expedia Availability/Prices Updates Outage Type: Incident Duration: 1 hour and 33 minutes Affected Components: Expedia May 12, 17:41:00 GMT+0 - Identified - Expedia is experiencing an outage involving the retrieval of Sirvoy availability and price updates, they are not being accepted by Expedia. There could be a resulting temporary discrepancy of availability and prices while this outage lasts. All pending updates will be retried, so no action is needed on your part. May 12, 19:14:00 GMT+0 - Resolved - Expedia experienced an outage that has been solved now. The outage involved Expedia not accepting Sirvoy updates of availability and prices. There could have been a temporary discrepancy of availability if you received bookings during this outage period. Expedia fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part. Type: Incident

Duration: 1 hour and 33 minutes

Affected Components:

<p><small>May <var data-var='date'> 12</var>, <var data-var='time'>17:41:00</var> GMT+0</small><br><strong>Identified</strong> - Expedia is experiencing an outage involving the retrieval of Sirvoy availability and price updates, they are not being accepted by Expedia. There could be a resulting temporary discrepancy of availability and prices while this outage lasts. All pending updates will be retried, so no action is needed on your part..</p> <p><small>May <var data-var='date'> 12</var>, <var data-var='time'>19:14:00</var> GMT+0</small><br><strong>Resolved</strong> - Expedia experienced an outage that has been solved now. The outage involved Expedia not accepting Sirvoy updates of availability and prices. There could have been a temporary discrepancy of availability if you received bookings during this outage period. Expedia fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part..</p> ]]> Tue, 12 May 2026 17:41:00 +0000 https://status.sirvoy.com/incident/cmp32161l04i1qgud3539nkt1 https://status.sirvoy.com/incident/cmp32161l04i1qgud3539nkt1 SMS Delivery Issue Type: Incident Duration: 1 day, 13 hours and 31 minutes Affected Components: SMS May 7, 07:29:00 GMT+0 - Identified - We are currently experiencing an issue affecting SMS delivery for some customers. This is due to an outage with our third-party SMS providers. As a result, some SMS messages may be delayed or not delivered at this time. Messages currently queued will be delivered automatically once service has been restored. Our provider is actively working to resolve the issue, and we are monitoring the situation closely. We apologise for any inconvenience this may cause and will provide further updates as soon as more information becomes available. May 8, 21:00:00 GMT+0 - Resolved - The problem that resulted in non-delivery of SMS has been resolved. This was caused by a temporary performance issue at our SMS providers side. If you sent any SMS during the outage period please make sure to resend it. Area affected: Globally Type: Incident

Duration: 1 day, 13 hours and 31 minutes

Affected Components:

<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>07:29:00</var> GMT+0</small><br><strong>Identified</strong> - We are currently experiencing an issue affecting SMS delivery for some customers. This is due to an outage with our third-party SMS providers. As a result, some SMS messages may be delayed or not delivered at this time. Messages currently queued will be delivered automatically once service has been restored. Our provider is actively working to resolve the issue, and we are monitoring the situation closely. We apologise for any inconvenience this may cause and will provide further updates as soon as more information becomes available. .</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br><strong>Resolved</strong> - The problem that resulted in non-delivery of SMS has been resolved. This was caused by a temporary performance issue at our SMS providers side. If you sent any SMS during the outage period please make sure to resend it. Area affected: Globally.</p> ]]> Thu, 7 May 2026 07:29:00 +0000 https://status.sirvoy.com/incident/cmovcxvpz03zuznbdejqpcoa3 https://status.sirvoy.com/incident/cmovcxvpz03zuznbdejqpcoa3 Agoda Booking Retrieval Outage Type: Incident Duration: 3 hours and 43 minutes Affected Components: Agoda Apr 20, 11:35:00 GMT+0 - Resolved - The Agoda outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 24h. If you seem to have bookings from Agoda that don’t appear in Sirvoy even after 24h then please email us at support@sirvoy.com to let us know and include your username in the email. Apr 20, 07:52:00 GMT+0 - Identified - Agoda is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Agoda will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Agoda if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves. Type: Incident

Duration: 3 hours and 43 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>11:35:00</var> GMT+0</small><br><strong>Resolved</strong> - The Agoda outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 24h. If you seem to have bookings from Agoda that don’t appear in Sirvoy even after 24h then please email us at support@sirvoy.com to let us know and include your username in the email..</p> <p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>07:52:00</var> GMT+0</small><br><strong>Identified</strong> - Agoda is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Agoda will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Agoda if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves..</p> ]]> Mon, 20 Apr 2026 07:52:00 +0000 https://status.sirvoy.com/incident/cmo71xf2m01cuoo00lk3h2cxj https://status.sirvoy.com/incident/cmo71xf2m01cuoo00lk3h2cxj Expedia Outage Type: Incident Duration: 2 hours and 11 minutes Affected Components: Expedia Apr 19, 10:59:00 GMT+0 - Identified - Expedia is experiencing an outage that has not yet been resolved. This is affecting both the retrieval of bookings into Sirvoy and Expedia’s acceptance of Sirvoy availability and price updates. **Booking retrieval (Expedia → Sirvoy):** During the outage, bookings and updates made in Expedia are not sent to Sirvoy. After the outage is resolved, Expedia will send any missing bookings and updates to Sirvoy over time. Expedia offers fallback solutions for receiving bookings, modifications, and cancellations by email during outages. **Availability and price updates (Sirvoy → Expedia):** Availability and price updates are not being accepted by Expedia. This may result in a temporary discrepancy in availability and prices while the outage lasts. All pending updates will be retried, so no action is needed on your part. There will be an update here when the outage resolves. Apr 19, 14:42:00 GMT+0 - Resolved - The Expedia outage has now been resolved. The issue affected both the retrieval of bookings into Sirvoy and Expedia’s acceptance of availability and price updates. **Booking retrieval:** Bookings made on Expedia during the outage will automatically import to Sirvoy over time. Please verify a few hours after the outage has ended that all bookings were imported successfully. Expedia offers fallback solutions for receiving bookings, modifications, and cancellations by email during outages. **Availability and prices:** Expedia has fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part. If you received bookings during the outage period, there could have been a temporary discrepancy of availability. Type: Incident

Duration: 2 hours and 11 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>10:59:00</var> GMT+0</small><br><strong>Identified</strong> - Expedia is experiencing an outage that has not yet been resolved. This is affecting both the retrieval of bookings into Sirvoy and Expedia’s acceptance of Sirvoy availability and price updates. **Booking retrieval (Expedia → Sirvoy):** During the outage, bookings and updates made in Expedia are not sent to Sirvoy. After the outage is resolved, Expedia will send any missing bookings and updates to Sirvoy over time. Expedia offers fallback solutions for receiving bookings, modifications, and cancellations by email during outages. **Availability and price updates (Sirvoy → Expedia):** Availability and price updates are not being accepted by Expedia. This may result in a temporary discrepancy in availability and prices while the outage lasts. All pending updates will be retried, so no action is needed on your part. There will be an update here when the outage resolves..</p> <p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>14:42:00</var> GMT+0</small><br><strong>Resolved</strong> - The Expedia outage has now been resolved. The issue affected both the retrieval of bookings into Sirvoy and Expedia’s acceptance of availability and price updates. **Booking retrieval:** Bookings made on Expedia during the outage will automatically import to Sirvoy over time. Please verify a few hours after the outage has ended that all bookings were imported successfully. Expedia offers fallback solutions for receiving bookings, modifications, and cancellations by email during outages. **Availability and prices:** Expedia has fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part. If you received bookings during the outage period, there could have been a temporary discrepancy of availability. .</p> ]]> Sun, 19 Apr 2026 10:59:00 +0000 https://status.sirvoy.com/incident/cmo5za5vp07aorpfj9ks9z6xr https://status.sirvoy.com/incident/cmo5za5vp07aorpfj9ks9z6xr Expedia Outage Type: Incident Duration: 1 hour and 25 minutes Affected Components: Expedia Apr 4, 19:00:00 GMT+0 - Identified - Expedia is experiencing an outage that has not yet been resolved. This is affecting both the retrieval of bookings into Sirvoy and Expedia’s acceptance of Sirvoy availability and price updates. **Booking retrieval (Expedia → Sirvoy):** During the outage, bookings and updates made in Expedia are not sent to Sirvoy. After the outage is resolved, Expedia will send any missing bookings and updates to Sirvoy over time. Expedia offers fallback solutions for receiving bookings, modifications, and cancellations by email during outages. **Availability and price updates (Sirvoy → Expedia):** Availability and price updates are not being accepted by Expedia. This may result in a temporary discrepancy in availability and prices while the outage lasts. All pending updates will be retried, so no action is needed on your part. There will be an update here when the outage resolves. Apr 4, 20:25:00 GMT+0 - Resolved - The Expedia outage has now been resolved. The issue affected both the retrieval of bookings into Sirvoy and Expedia’s acceptance of availability and price updates. **Booking retrieval:** Bookings made on Expedia during the outage will automatically import to Sirvoy over time. Please verify a few hours after the outage has ended that all bookings were imported successfully. Expedia offers fallback solutions for receiving bookings, modifications, and cancellations by email during outages. **Availability and prices:** Expedia has fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part. If you received bookings during the outage period, there could have been a temporary discrepancy of availability. Type: Incident

Duration: 1 hour and 25 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Identified</strong> - Expedia is experiencing an outage that has not yet been resolved. This is affecting both the retrieval of bookings into Sirvoy and Expedia’s acceptance of Sirvoy availability and price updates. **Booking retrieval (Expedia → Sirvoy):** During the outage, bookings and updates made in Expedia are not sent to Sirvoy. After the outage is resolved, Expedia will send any missing bookings and updates to Sirvoy over time. Expedia offers fallback solutions for receiving bookings, modifications, and cancellations by email during outages. **Availability and price updates (Sirvoy → Expedia):** Availability and price updates are not being accepted by Expedia. This may result in a temporary discrepancy in availability and prices while the outage lasts. All pending updates will be retried, so no action is needed on your part. There will be an update here when the outage resolves..</p> <p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>20:25:00</var> GMT+0</small><br><strong>Resolved</strong> - The Expedia outage has now been resolved. The issue affected both the retrieval of bookings into Sirvoy and Expedia’s acceptance of availability and price updates. **Booking retrieval:** Bookings made on Expedia during the outage will automatically import to Sirvoy over time. Please verify a few hours after the outage has ended that all bookings were imported successfully. Expedia offers fallback solutions for receiving bookings, modifications, and cancellations by email during outages. **Availability and prices:** Expedia has fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part. If you received bookings during the outage period, there could have been a temporary discrepancy of availability. .</p> ]]> Sat, 4 Apr 2026 19:00:00 +0000 https://status.sirvoy.com/incident/cmno6tjq800athepnm42dppwc https://status.sirvoy.com/incident/cmno6tjq800athepnm42dppwc Booking.com Booking Retrieval Outage Type: Incident Duration: 23 minutes Affected Components: Booking.com Mar 29, 02:45:00 GMT+0 - Identified - Booking.com is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Booking.com will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Booking.com if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves. Mar 29, 03:08:00 GMT+0 - Resolved - The Booking.com outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 36h. If you seem to have bookings from Booking.com that don't appear in Sirvoy even after 36h then please email us at [support@sirvoy.com](mailto:support@sirvoy.com) to let us know and include your username in the email. Any cancellations made during the outage will not be automatically retrieved. If you did receive cancellations, please email us the reservation number and we will be able to update the booking to its cancelled status. Type: Incident

Duration: 23 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 29</var>, <var data-var='time'>02:45:00</var> GMT+0</small><br><strong>Identified</strong> - Booking.com is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Booking.com will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Booking.com if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves..</p> <p><small>Mar <var data-var='date'> 29</var>, <var data-var='time'>03:08:00</var> GMT+0</small><br><strong>Resolved</strong> - The Booking.com outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 36h. If you seem to have bookings from Booking.com that don't appear in Sirvoy even after 36h then please email us at [support@sirvoy.com](mailto:support@sirvoy.com) to let us know and include your username in the email. Any cancellations made during the outage will not be automatically retrieved. If you did receive cancellations, please email us the reservation number and we will be able to update the booking to its cancelled status..</p> ]]> Sun, 29 Mar 2026 02:45:00 +0000 https://status.sirvoy.com/incident/cmncqn50w002n12wbze5ou65e https://status.sirvoy.com/incident/cmncqn50w002n12wbze5ou65e Booking.com Booking Retrieval Outage Type: Incident Duration: 1 hour and 17 minutes Affected Components: Booking.com Mar 24, 16:00:00 GMT+0 - Resolved - The Booking.com outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 36h. If you seem to have bookings from Booking.com that don't appear in Sirvoy even after 36h then please email us at [support@sirvoy.com](mailto:support@sirvoy.com) to let us know and include your username in the email. Any cancellations made during the outage will not be automatically retrieved. If you did receive cancellations, please email us the reservation number and we will be able to update the booking to its cancelled status. Mar 24, 14:43:00 GMT+0 - Identified - Booking.com is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Booking.com will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Booking.com if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves. Type: Incident

Duration: 1 hour and 17 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Resolved</strong> - The Booking.com outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 36h. If you seem to have bookings from Booking.com that don't appear in Sirvoy even after 36h then please email us at [support@sirvoy.com](mailto:support@sirvoy.com) to let us know and include your username in the email. Any cancellations made during the outage will not be automatically retrieved. If you did receive cancellations, please email us the reservation number and we will be able to update the booking to its cancelled status..</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>14:43:00</var> GMT+0</small><br><strong>Identified</strong> - Booking.com is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Booking.com will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Booking.com if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves..</p> ]]> Tue, 24 Mar 2026 14:43:00 +0000 https://status.sirvoy.com/incident/cmn4te8rp05559nyzg7yg5jjq https://status.sirvoy.com/incident/cmn4te8rp05559nyzg7yg5jjq Airbnb Availability/Prices Updates Outage Type: Incident Duration: 1 hour and 25 minutes Affected Components: Airbnb Mar 24, 01:00:00 GMT+0 - Identified - Airbnb is experiencing an outage involving the retrieval of Sirvoy availability and price updates, they are not being accepted by Airbnb. There could be a resulting temporary discrepancy in availability and prices while this outage lasts. All pending updates will be retried, so no action is needed on your part. Mar 24, 02:25:00 GMT+0 - Resolved - Airbnb experienced an outage that has been solved now. The outage involved Airbnb not accepting Sirvoy updates of availability and prices. There could have been a temporary discrepancy of availability if you received bookings during this outage period. Airbnb fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part. Type: Incident

Duration: 1 hour and 25 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Identified</strong> - Airbnb is experiencing an outage involving the retrieval of Sirvoy availability and price updates, they are not being accepted by Airbnb. There could be a resulting temporary discrepancy in availability and prices while this outage lasts. All pending updates will be retried, so no action is needed on your part..</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>02:25:00</var> GMT+0</small><br><strong>Resolved</strong> - Airbnb experienced an outage that has been solved now. The outage involved Airbnb not accepting Sirvoy updates of availability and prices. There could have been a temporary discrepancy of availability if you received bookings during this outage period. Airbnb fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part..</p> ]]> Tue, 24 Mar 2026 01:00:00 +0000 https://status.sirvoy.com/incident/cmn42p9l904yh34vkdoleoc7y https://status.sirvoy.com/incident/cmn42p9l904yh34vkdoleoc7y Sirvoy Vault Issue Type: Incident Duration: 1 hour and 41 minutes Affected Components: Sirvoy Vault Mar 17, 17:30:00 GMT+0 - Identified - An issue with the Sirvoy Vault is currently causing a crash error when using text message (SMS) authentication to retrieve credit card details. This affects the ability to view already saved credit card information in the “Booking” view. Viewing credit card details by using the Google Authenticator message still works as expected. Our team is actively working on a solution, and we will update this status once the issue is resolved. We apologize for the inconvenience. If you have any questions, please contact us at [support@sirvoy.com](mailto:support@sirvoy.com). Mar 17, 19:11:27 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 41 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 17</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br><strong>Identified</strong> - An issue with the Sirvoy Vault is currently causing a crash error when using text message (SMS) authentication to retrieve credit card details. This affects the ability to view already saved credit card information in the “Booking” view. Viewing credit card details by using the Google Authenticator message still works as expected. Our team is actively working on a solution, and we will update this status once the issue is resolved. We apologize for the inconvenience. If you have any questions, please contact us at [support@sirvoy.com](mailto:support@sirvoy.com)..</p> <p><small>Mar <var data-var='date'> 17</var>, <var data-var='time'>19:11:27</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 17 Mar 2026 17:30:00 +0000 https://status.sirvoy.com/incident/cmmv0qe25015cw3c73hsfhd6z https://status.sirvoy.com/incident/cmmv0qe25015cw3c73hsfhd6z Booking.com Booking Retrieval Outage Type: Incident Duration: 36 minutes Affected Components: Booking.com Mar 11, 13:40:00 GMT+0 - Identified - Booking.com is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Booking.com will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Booking.com if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves. Mar 11, 14:16:00 GMT+0 - Resolved - The Booking.com outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 36h. If you seem to have bookings from Booking.com that don't appear in Sirvoy even after 36h then please email us at [support@sirvoy.com](mailto:support@sirvoy.com) to let us know and include your username in the email. Any cancellations made during the outage will not be automatically retrieved. If you did receive cancellations, please email us the reservation number and we will be able to update the booking to its cancelled status. Type: Incident

Duration: 36 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>13:40:00</var> GMT+0</small><br><strong>Identified</strong> - Booking.com is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Booking.com will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Booking.com if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves..</p> <p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>14:16:00</var> GMT+0</small><br><strong>Resolved</strong> - The Booking.com outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 36h. If you seem to have bookings from Booking.com that don't appear in Sirvoy even after 36h then please email us at [support@sirvoy.com](mailto:support@sirvoy.com) to let us know and include your username in the email. Any cancellations made during the outage will not be automatically retrieved. If you did receive cancellations, please email us the reservation number and we will be able to update the booking to its cancelled status..</p> ]]> Wed, 11 Mar 2026 13:40:00 +0000 https://status.sirvoy.com/incident/cmmm3pl7m0462q0td73i1foha https://status.sirvoy.com/incident/cmmm3pl7m0462q0td73i1foha BookVisit Booking Retrieval Outage Type: Incident Duration: 18 hours and 58 minutes Affected Components: BookVisit Mar 10, 15:00:00 GMT+0 - Identified - BookVisit is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in BookVisit will not automatically transfer to your Sirvoy account during the outage. We advise you to manually register the bookings that have been made in BookVisit but have not been automatically registered in Sirvoy. Mar 11, 09:58:09 GMT+0 - Resolved - Check the [BookVisit import page](https://secured.sirvoy.com/settings/channels/bookvisit/import) for any bookings or updates that have not been applied in Sirvoy. If so, manually import them. If bookings were both automatically imported and manually added, delete the manually added versions. If you would like any help, contact us at support@sirvoy.com. Type: Incident

Duration: 18 hours and 58 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Identified</strong> - BookVisit is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in BookVisit will not automatically transfer to your Sirvoy account during the outage. We advise you to manually register the bookings that have been made in BookVisit but have not been automatically registered in Sirvoy..</p> <p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>09:58:09</var> GMT+0</small><br><strong>Resolved</strong> - Check the [BookVisit import page](https://secured.sirvoy.com/settings/channels/bookvisit/import) for any bookings or updates that have not been applied in Sirvoy. If so, manually import them. If bookings were both automatically imported and manually added, delete the manually added versions. If you would like any help, contact us at support@sirvoy.com..</p> ]]> Tue, 10 Mar 2026 15:00:00 +0000 https://status.sirvoy.com/incident/cmmkry10o046cvykhl2lgwwbt https://status.sirvoy.com/incident/cmmkry10o046cvykhl2lgwwbt Booking.com Booking Retrieval Outage Type: Incident Duration: 39 minutes Affected Components: Booking.com Mar 6, 10:10:00 GMT+0 - Identified - Booking.com is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Booking.com will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Booking.com if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves. Mar 6, 10:49:00 GMT+0 - Resolved - The Booking.com outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 36h. If you seem to have bookings from Booking.com that don't appear in Sirvoy even after 36h then please email us at [support@sirvoy.com](mailto:support@sirvoy.com) to let us know and include your username in the email. Any cancellations made during the outage will not be automatically retrieved. If you did receive cancellations, please email us the reservation number and we will be able to update the booking to its cancelled status. Type: Incident

Duration: 39 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>10:10:00</var> GMT+0</small><br><strong>Identified</strong> - Booking.com is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Booking.com will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Booking.com if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves..</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>10:49:00</var> GMT+0</small><br><strong>Resolved</strong> - The Booking.com outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 36h. If you seem to have bookings from Booking.com that don't appear in Sirvoy even after 36h then please email us at [support@sirvoy.com](mailto:support@sirvoy.com) to let us know and include your username in the email. Any cancellations made during the outage will not be automatically retrieved. If you did receive cancellations, please email us the reservation number and we will be able to update the booking to its cancelled status..</p> ]]> Fri, 6 Mar 2026 10:10:00 +0000 https://status.sirvoy.com/incident/cmmeqzcek052f5rolxtyvc7wt https://status.sirvoy.com/incident/cmmeqzcek052f5rolxtyvc7wt Booking.com Booking Retrieval Outage Type: Incident Duration: 3 days, 20 hours and 4 minutes Affected Components: Booking.com Mar 5, 11:01:00 GMT+0 - Identified - Booking.com is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Booking.com will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Booking.com if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves. Mar 5, 11:33:00 GMT+0 - Resolved - The [Booking.com](http://Booking.com) outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 36h. If you seem to have bookings from [Booking.com](http://Booking.com) that don't appear in Sirvoy even after 36h then please email us at [**support@sirvoy.com**](mailto:support@sirvoy.com) to let us know and include your username in the email. Any cancellations made during the outage will not be automatically retrieved. If you did receive cancellations, please email us the reservation number and we will be able to update the booking to its cancelled status. Type: Incident

Duration: 3 days, 20 hours and 4 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>11:01:00</var> GMT+0</small><br><strong>Identified</strong> - Booking.com is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Booking.com will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Booking.com if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>11:33:00</var> GMT+0</small><br><strong>Resolved</strong> - The [Booking.com](http://Booking.com) outage has now been resolved. If you have received any bookings during the outage then they should be added automatically over the coming 36h. If you seem to have bookings from [Booking.com](http://Booking.com) that don't appear in Sirvoy even after 36h then please email us at [**support@sirvoy.com**](mailto:support@sirvoy.com) to let us know and include your username in the email. Any cancellations made during the outage will not be automatically retrieved. If you did receive cancellations, please email us the reservation number and we will be able to update the booking to its cancelled status..</p> ]]> Thu, 5 Mar 2026 11:01:00 +0000 https://status.sirvoy.com/incident/cmmiv8oyn009471j6q1lxoj17 https://status.sirvoy.com/incident/cmmiv8oyn009471j6q1lxoj17 BookVisit Booking Retrieval Outage Type: Incident Duration: 2 hours and 23 minutes Affected Components: BookVisit Mar 3, 19:18:00 GMT+0 - Resolved - Check the [BookVisit import page](https://secured.sirvoy.com/settings/channels/bookvisit/import) for any bookings or updates that have not been applied in Sirvoy. If so, manually import them. If bookings were both automatically imported and manually added, delete the manually added versions. If you would like any help, contact us at support@sirvoy.com. Mar 3, 16:55:00 GMT+0 - Identified - BookVisit is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in BookVisit will not automatically transfer to your Sirvoy account during the outage. We advise you to manually register the bookings that have been made in BookVisit but have not been automatically registered in Sirvoy. Type: Incident

Duration: 2 hours and 23 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>19:18:00</var> GMT+0</small><br><strong>Resolved</strong> - Check the [BookVisit import page](https://secured.sirvoy.com/settings/channels/bookvisit/import) for any bookings or updates that have not been applied in Sirvoy. If so, manually import them. If bookings were both automatically imported and manually added, delete the manually added versions. If you would like any help, contact us at support@sirvoy.com..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>16:55:00</var> GMT+0</small><br><strong>Identified</strong> - BookVisit is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in BookVisit will not automatically transfer to your Sirvoy account during the outage. We advise you to manually register the bookings that have been made in BookVisit but have not been automatically registered in Sirvoy..</p> ]]> Tue, 3 Mar 2026 16:55:00 +0000 https://status.sirvoy.com/incident/cmmavoes20bk95ita7qf9emw8 https://status.sirvoy.com/incident/cmmavoes20bk95ita7qf9emw8 Airbnb Availability/Prices Updates Outage Type: Incident Duration: 40 minutes Affected Components: Airbnb Feb 28, 12:08:00 GMT+0 - Identified - Airbnb is experiencing an outage involving the retrieval of Sirvoy availability and price updates, they are not being accepted by Airbnb. There could be a resulting temporary discrepancy in availability and prices while this outage lasts. All pending updates will be retried, so no action is needed on your part. Feb 28, 12:48:00 GMT+0 - Resolved - Airbnb experienced an outage that has been solved now. The outage involved Airbnb not accepting Sirvoy updates of availability and prices. There could have been a temporary discrepancy of availability if you received bookings during this outage period. Airbnb fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part. Type: Incident

Duration: 40 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>12:08:00</var> GMT+0</small><br><strong>Identified</strong> - Airbnb is experiencing an outage involving the retrieval of Sirvoy availability and price updates, they are not being accepted by Airbnb. There could be a resulting temporary discrepancy in availability and prices while this outage lasts. All pending updates will be retried, so no action is needed on your part..</p> <p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>12:48:00</var> GMT+0</small><br><strong>Resolved</strong> - Airbnb experienced an outage that has been solved now. The outage involved Airbnb not accepting Sirvoy updates of availability and prices. There could have been a temporary discrepancy of availability if you received bookings during this outage period. Airbnb fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part..</p> ]]> Sat, 28 Feb 2026 12:08:00 +0000 https://status.sirvoy.com/incident/cmm8zdrtu06eq14itjwp5il7g https://status.sirvoy.com/incident/cmm8zdrtu06eq14itjwp5il7g Booking.com Booking Retrieval Outage Type: Incident Duration: 4 hours and 41 minutes Affected Components: Booking.com Feb 27, 19:46:00 GMT+0 - Resolved - This incident has been resolved. Feb 27, 15:05:00 GMT+0 - Identified - Booking.com is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Booking.com will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Booking.com if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves. Type: Incident

Duration: 4 hours and 41 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>19:46:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>15:05:00</var> GMT+0</small><br><strong>Identified</strong> - Booking.com is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Booking.com will not automatically transfer to your Sirvoy account during the outage. However after the outage we will over time add any missing bookings. If you wish to be able to add any missed bookings even during the outage then we strongly advise that you check with Booking.com if you can set up a "fall back" method through their extranet that will enable you to receive e-mail or faxes with the bookings received from their channel even during outages. Please be aware that any bookings sent to you through the fallback solution will not be automatically transferred after the outage ended but have to be manually transferred to your Sirvoy account by yourselves..</p> ]]> Fri, 27 Feb 2026 15:05:00 +0000 https://status.sirvoy.com/incident/cmm56k23100eg13n309tqbn34 https://status.sirvoy.com/incident/cmm56k23100eg13n309tqbn34 Booking.com Availability/Prices Updates Outage Type: Incident Duration: 1 hour and 10 minutes Affected Components: Booking.com Feb 27, 15:16:00 GMT+0 - Resolved - Booking.com experienced an outage that has been solved now. The outage involved Booking.com not accepting Sirvoy updates of availability and prices. There could have been a temporary discrepancy of availability if you received bookings during this outage period. Booking.com fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part. Feb 27, 14:06:00 GMT+0 - Identified - Booking.com is experiencing an outage involving the retrieval of Sirvoy availability and price updates, they are not being accepted by Booking.com. There could be a resulting temporary discrepancy of availability and prices while this outage lasts. All pending updates will be retried, so no action is needed on your part. Type: Incident

Duration: 1 hour and 10 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>15:16:00</var> GMT+0</small><br><strong>Resolved</strong> - Booking.com experienced an outage that has been solved now. The outage involved Booking.com not accepting Sirvoy updates of availability and prices. There could have been a temporary discrepancy of availability if you received bookings during this outage period. Booking.com fixed the issue, all pending updates were retried, and both systems have now been updated accordingly. No action is needed on your part..</p> <p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>14:06:00</var> GMT+0</small><br><strong>Identified</strong> - Booking.com is experiencing an outage involving the retrieval of Sirvoy availability and price updates, they are not being accepted by Booking.com. There could be a resulting temporary discrepancy of availability and prices while this outage lasts. All pending updates will be retried, so no action is needed on your part..</p> ]]> Fri, 27 Feb 2026 14:06:00 +0000 https://status.sirvoy.com/incident/cmm4ziaa613htx4rz6c63b50h https://status.sirvoy.com/incident/cmm4ziaa613htx4rz6c63b50h Email Delivery Issue Type: Incident Duration: 2 days, 8 hours and 5 minutes Affected Components: Emails Feb 26, 02:00:00 GMT+0 - Resolved - The issue that caused delays in email delivery to Microsoft domains ([live.com](http://live.com), [hotmail.com](http://hotmail.com), [outlook.com](http://outlook.com), [msn.com](http://msn.com)) has been resolved. Most affected emails have now been delivered. However, some messages may have failed due to timeouts. Please verify delivery and resend if necessary. We apologize for any inconvenience caused. Feb 23, 17:55:00 GMT+0 - Identified - At the moment, some customers may experience delays in email delivery to Microsoft email domains, including live.com, hotmail.com, and outlook.com. Emails are temporarily delayed but are still being retried automatically. We are closely monitoring the situation together with our email provider. We apologize for any inconvenience and will share further updates as soon as more information becomes available. Type: Incident

Duration: 2 days, 8 hours and 5 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br><strong>Resolved</strong> - The issue that caused delays in email delivery to Microsoft domains ([live.com](http://live.com), [hotmail.com](http://hotmail.com), [outlook.com](http://outlook.com), [msn.com](http://msn.com)) has been resolved. Most affected emails have now been delivered. However, some messages may have failed due to timeouts. Please verify delivery and resend if necessary. We apologize for any inconvenience caused..</p> <p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>17:55:00</var> GMT+0</small><br><strong>Identified</strong> - At the moment, some customers may experience delays in email delivery to Microsoft email domains, including live.com, hotmail.com, and outlook.com. Emails are temporarily delayed but are still being retried automatically. We are closely monitoring the situation together with our email provider. We apologize for any inconvenience and will share further updates as soon as more information becomes available..</p> ]]> Mon, 23 Feb 2026 17:55:00 +0000 https://status.sirvoy.com/incident/cmm0v6v4t02cdt6rlt2w6798v https://status.sirvoy.com/incident/cmm0v6v4t02cdt6rlt2w6798v Live Support Temporary Unavailable Type: Incident Duration: 44 minutes Affected Components: Support Desk Feb 21, 10:00:14 GMT+0 - Identified - A third-party provider is experiencing an issue which is currently causing our **Support phone** to malfunction. We will update the blog when the problem has been resolved, but in the meantime please feel free to use the chat function or send an email to support@sirvoy.com and we will get back to you as soon as possible. We apologise for any inconvenience. Feb 21, 10:44:14 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 44 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 21</var>, <var data-var='time'>10:00:14</var> GMT+0</small><br><strong>Identified</strong> - A third-party provider is experiencing an issue which is currently causing our **Support phone** to malfunction. We will update the blog when the problem has been resolved, but in the meantime please feel free to use the chat function or send an email to support@sirvoy.com and we will get back to you as soon as possible. We apologise for any inconvenience..</p> <p><small>Feb <var data-var='date'> 21</var>, <var data-var='time'>10:44:14</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 21 Feb 2026 10:00:14 +0000 https://status.sirvoy.com/incident/cmlw82wnq07r9ngh0rwcs9rrc https://status.sirvoy.com/incident/cmlw82wnq07r9ngh0rwcs9rrc Live Support Temporary Unavailable Type: Incident Duration: 7 hours and 18 minutes Affected Components: Support Desk Feb 21, 09:00:00 GMT+0 - Identified - A third-party provider is experiencing an issue which is currently causing our **Support phone** to malfunction. We will update the blog when the problem has been resolved, but in the meantime please feel free to **contact us by chat or send an email** to support@sirvoy.com and we will get back to you as soon as possible. We apologise for any inconvenience. Feb 21, 16:18:28 GMT+0 - Resolved - A third-party provider recently experienced an issue which caused a temporary outage to our Support chat and phone lines. We would like to inform you that this problem has since been resolved and normal service is resumed. We apologise for any inconvenience. Type: Incident

Duration: 7 hours and 18 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 21</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> - A third-party provider is experiencing an issue which is currently causing our **Support phone** to malfunction. We will update the blog when the problem has been resolved, but in the meantime please feel free to **contact us by chat or send an email** to support@sirvoy.com and we will get back to you as soon as possible. We apologise for any inconvenience..</p> <p><small>Feb <var data-var='date'> 21</var>, <var data-var='time'>16:18:28</var> GMT+0</small><br><strong>Resolved</strong> - A third-party provider recently experienced an issue which caused a temporary outage to our Support chat and phone lines. We would like to inform you that this problem has since been resolved and normal service is resumed. We apologise for any inconvenience..</p> ]]> Sat, 21 Feb 2026 09:00:00 +0000 https://status.sirvoy.com/incident/cmlw84q4i07sf1421v06wsiti https://status.sirvoy.com/incident/cmlw84q4i07sf1421v06wsiti Maintenance in Progress – Booking.com Integration Type: Maintenance Duration: 40 minutes Affected Components: Booking.com Aug 14, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 14, 06:40:00 GMT+0 - Completed - Maintenance has completed successfully Aug 14, 06:00:00 GMT+0 - Identified - We are currently performing brief maintenance on the [Booking.com](http://Booking.com) integration. During this time, **new reservations coming from** [**Booking.com**](http://Booking.com) **are temporarily delayed**, and **updates sent to** [**Booking.com**](http://Booking.com) **are paused**. Please rest assured that **any reservations or updates that occur during this window will be automatically processed** as soon as the maintenance is completed. Thank you for your understanding. — The Sirvoy Team Type: Maintenance

Duration: 40 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>06:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>06:40:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are currently performing brief maintenance on the [Booking.com](http://Booking.com) integration. During this time, **new reservations coming from** [**Booking.com**](http://Booking.com) **are temporarily delayed**, and **updates sent to** [**Booking.com**](http://Booking.com) **are paused**. Please rest assured that **any reservations or updates that occur during this window will be automatically processed** as soon as the maintenance is completed. Thank you for your understanding. — The Sirvoy Team.</p> ]]> Thu, 14 Aug 2025 06:00:00 +0000 https://status.sirvoy.com/maintenance/cmeazof2y0006detyvngoawsp https://status.sirvoy.com/maintenance/cmeazof2y0006detyvngoawsp Upcoming Scheduled Maintenance Type: Maintenance Duration: 5 minutes Affected Components: Booking.com Aug 12, 14:31:00 GMT+0 - Completed - Maintenance has completed successfully Aug 12, 14:26:01 GMT+0 - Identified - Maintenance is now in progress Aug 12, 14:26:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Type: Maintenance

Duration: 5 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>14:31:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>14:26:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>14:26:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> ]]> Tue, 12 Aug 2025 14:26:00 +0000 https://status.sirvoy.com/maintenance/cme8msmjh00n411f6v1xs4kur https://status.sirvoy.com/maintenance/cme8msmjh00n411f6v1xs4kur Upcoming Scheduled Maintenance Type: Maintenance Affected Components: Backend, PayPal, Myallocator, Payer, Peppol, Support Desk, Website Builder, Siteminder, TripAdvisor, Stripe, iCal, Booking Engine, Hostelworld, Payson, Emails, SMS, Agoda, Google Hotel Ads, Website, BookVisit, Booking.com, Sirvoy Vault, Expedia, Airbnb Nov 4, 04:00:00 GMT+0 - Completed - In order to improve security, reliability, and operational performance, we have scheduled routine maintenance on Sirvoy’s servers. Our system will be temporarily unavailable on 2024-11-04 at 04:00 AM UTC Please note: * Procure any information you may need from the system before the scheduled maintenance begins. * Although channel bookings should be retrieved automatically when the maintenance is over, we recommend manually verifying them. * If connected to Expedia, set up the "fallback" solution there to ensure that you receive bookings through email or fax during longer outages. Type: Maintenance

Affected Components: , , , , , , , , , , , , , , , , , , , , , , ,

<p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br><strong>Completed</strong> - In order to improve security, reliability, and operational performance, we have scheduled routine maintenance on Sirvoy’s servers. Our system will be temporarily unavailable on 2024-11-04 at 04:00 AM UTC Please note: * Procure any information you may need from the system before the scheduled maintenance begins. * Although channel bookings should be retrieved automatically when the maintenance is over, we recommend manually verifying them. * If connected to Expedia, set up the "fallback" solution there to ensure that you receive bookings through email or fax during longer outages..</p> ]]> Mon, 4 Nov 2024 04:00:00 +0000 https://status.sirvoy.com/maintenance/cm30892ij000u6f6k1cyr8xh8 https://status.sirvoy.com/maintenance/cm30892ij000u6f6k1cyr8xh8