Sirvoy Status - Incident history https://status.sirvoy.com Sirvoy Thu, 6 Aug 2026 09:35:00 +0000 Booking.com Booking Retrieval Outage Type: Incident Duration: 4 hours and 6 minutes Affected Components: Booking.com Aug 6, 13:41: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. Aug 6, 09: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: 4 hours and 6 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>13:41: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>Aug <var data-var='date'> 6</var>, <var data-var='time'>09: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, 6 Aug 2026 09:35:00 +0000 https://status.sirvoy.com/incident/cmshc355y03y71bo3bw50934g https://status.sirvoy.com/incident/cmshc355y03y71bo3bw50934g Booking.com Booking Retrieval Outage Type: Incident Duration: 3 hours and 34 minutes Affected Components: Booking.com Aug 5, 12:26: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. Aug 5, 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. Type: Incident

Duration: 3 hours and 34 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>12:26: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>Aug <var data-var='date'> 5</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> ]]> Wed, 5 Aug 2026 12:26:00 +0000 https://status.sirvoy.com/incident/cmsg2wmsm02j30zjsilx21bgd https://status.sirvoy.com/incident/cmsg2wmsm02j30zjsilx21bgd Booking.com Booking Retrieval Outage Type: Incident Duration: 20 minutes Affected Components: Security, Booking.com Jul 24, 13:19: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. Jul 24, 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. Type: Incident

Duration: 20 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>13:19: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>Jul <var data-var='date'> 24</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> ]]> Fri, 24 Jul 2026 13:19:00 +0000 https://status.sirvoy.com/incident/cmryzp1m009av0zruhhbt94z1 https://status.sirvoy.com/incident/cmryzp1m009av0zruhhbt94z1 Expedia Availability/Prices Updates Outage Type: Incident Duration: 15 minutes Affected Components: Expedia Jul 24, 08:55: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. Jul 24, 09:10: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: 15 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>08:55: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>Jul <var data-var='date'> 24</var>, <var data-var='time'>09:10: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> ]]> Fri, 24 Jul 2026 08:55:00 +0000 https://status.sirvoy.com/incident/cms2scg1m0r1v0kqd99d1tplk https://status.sirvoy.com/incident/cms2scg1m0r1v0kqd99d1tplk Live Chat Support Issues Type: Incident Duration: 9 hours and 37 minutes Affected Components: Support Desk Jul 15, 07:00:00 GMT+0 - Identified - A third-party provider is experiencing an issue which is currently causing our Support chat to malfunction. We will update the blog when the problem has been resolved, but in the meantime chat support might take longer than expected to be attended to. You can also reach us by sending an email to [support@sirvoy.com](mailto:support@sirvoy.com) and we will get back to you as soon as possible. We apologise for any inconvenience. Jul 15, 16:37:00 GMT+0 - Resolved - A third-party provider recently experienced an issue which caused a temporary outage to our Support chat. 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: 9 hours and 37 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Identified</strong> - A third-party provider is experiencing an issue which is currently causing our Support chat to malfunction. We will update the blog when the problem has been resolved, but in the meantime chat support might take longer than expected to be attended to. You can also reach us by sending an email to [support@sirvoy.com](mailto:support@sirvoy.com) and we will get back to you as soon as possible. We apologise for any inconvenience..</p> <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>16:37:00</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. We would like to inform you that this problem has since been resolved and normal service is resumed. We apologise for any inconvenience..</p> ]]> Wed, 15 Jul 2026 07:00:00 +0000 https://status.sirvoy.com/incident/cmrnj8waf01uy13mohvxgon1u https://status.sirvoy.com/incident/cmrnj8waf01uy13mohvxgon1u Booking.com Booking Retrieval Outage Type: Incident Duration: 37 minutes Affected Components: Booking.com Jul 14, 12:58: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. Jul 14, 13:35:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 37 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>12:58: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>Jul <var data-var='date'> 14</var>, <var data-var='time'>13:35:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 14 Jul 2026 12:58:00 +0000 https://status.sirvoy.com/incident/cmrkoyfxq0b8s0zo2wwk4ee98 https://status.sirvoy.com/incident/cmrkoyfxq0b8s0zo2wwk4ee98 Hostelworld Booking Retrieval Outage Type: Incident Duration: 54 minutes Affected Components: Hostelworld Jul 8, 03:30:42 GMT+0 - Identified - Hostelworld is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Hostelworld 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 Hostelworld 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. Jul 8, 04:25:00 GMT+0 - Resolved - The Hostelworld 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 Hostelworld 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. Type: Incident

Duration: 54 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>03:30:42</var> GMT+0</small><br><strong>Identified</strong> - Hostelworld is experiencing an outage that hasn't yet been resolved. Please be aware that bookings made in Hostelworld 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 Hostelworld 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>Jul <var data-var='date'> 8</var>, <var data-var='time'>04:25:00</var> GMT+0</small><br><strong>Resolved</strong> - The Hostelworld 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 Hostelworld 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> ]]> Wed, 8 Jul 2026 03:30:42 +0000 https://status.sirvoy.com/incident/cmrbli4xm03lr0rpdvi6q3gd1 https://status.sirvoy.com/incident/cmrbli4xm03lr0rpdvi6q3gd1 Hostelworld Availability/Prices Updates Outage Type: Incident Duration: 55 minutes Affected Components: Hostelworld Jul 8, 03:30:05 GMT+0 - Identified - Hostelworld is experiencing an outage involving the retrieval of Sirvoy availability and price updates, they are not being accepted by Hostelworld. 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. Jul 8, 04:25:00 GMT+0 - Resolved - Hostelworld experienced an outage that has been solved now. The outage involved Hostelworld 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. Hostelworld 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: 55 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>03:30:05</var> GMT+0</small><br><strong>Identified</strong> - Hostelworld is experiencing an outage involving the retrieval of Sirvoy availability and price updates, they are not being accepted by Hostelworld. 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>Jul <var data-var='date'> 8</var>, <var data-var='time'>04:25:00</var> GMT+0</small><br><strong>Resolved</strong> - Hostelworld experienced an outage that has been solved now. The outage involved Hostelworld 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. Hostelworld 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, 8 Jul 2026 03:30:05 +0000 https://status.sirvoy.com/incident/cmrbll8ym03xi0kpd4qa03n73 https://status.sirvoy.com/incident/cmrbll8ym03xi0kpd4qa03n73 Booking.com Booking Retrieval Outage Type: Incident Duration: 2 hours and 46 minutes Affected Components: Booking.com Jun 30, 19:39: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. Jun 30, 22:25: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: 2 hours and 46 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>19:39: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>Jun <var data-var='date'> 30</var>, <var data-var='time'>22:25: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> ]]> Tue, 30 Jun 2026 19:39:00 +0000 https://status.sirvoy.com/incident/cmr12vrgb00cf0rmoerb9k94z https://status.sirvoy.com/incident/cmr12vrgb00cf0rmoerb9k94z Booking.com Booking Retrieval Outage Type: Incident Duration: 14 minutes Affected Components: Booking.com Jun 29, 09: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. Jun 29, 09:59: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: 14 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 29</var>, <var data-var='time'>09: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>Jun <var data-var='date'> 29</var>, <var data-var='time'>09:59: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> ]]> Mon, 29 Jun 2026 09:45:00 +0000 https://status.sirvoy.com/incident/cmqz2qfwo01jh2ipnxw1tn3r1 https://status.sirvoy.com/incident/cmqz2qfwo01jh2ipnxw1tn3r1 Expedia Availability/Prices Updates Outage Type: Incident Duration: 2 hours and 28 minutes Affected Components: Expedia Jun 25, 08:22: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. Jun 25, 11:30: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: 2 hours and 28 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>08:22: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>Jun <var data-var='date'> 25</var>, <var data-var='time'>11:30: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> ]]> Thu, 25 Jun 2026 08:22:00 +0000 https://status.sirvoy.com/incident/cmqt9ns8a0crm2jru1dmw2x8p https://status.sirvoy.com/incident/cmqt9ns8a0crm2jru1dmw2x8p Email Delivery Issue Type: Incident Duration: 15 minutes Affected Components: Emails Jun 24, 18:05:00 GMT+0 - Identified - At the moment some of our customers may experience non-delivery of emails. We apologize for any inconvenience and are working to resolve this problem as soon as possible. We will update this blog as soon as we have more information. Jun 24, 18:20:00 GMT+0 - Resolved - The problem that resulted in non-delivery of email has been resolved. This was caused by a temporary performance issue at our email provider's side. If you sent any email during the outage period please make sure to resend it. Area affected: Globally/Europe/America/Asia Type: Incident

Duration: 15 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>18:05:00</var> GMT+0</small><br><strong>Identified</strong> - At the moment some of our customers may experience non-delivery of emails. We apologize for any inconvenience and are working to resolve this problem as soon as possible. We will update this blog as soon as we have more information..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>18:20:00</var> GMT+0</small><br><strong>Resolved</strong> - The problem that resulted in non-delivery of email has been resolved. This was caused by a temporary performance issue at our email provider's side. If you sent any email during the outage period please make sure to resend it. Area affected: Globally/Europe/America/Asia.</p> ]]> Wed, 24 Jun 2026 18:05:00 +0000 https://status.sirvoy.com/incident/cmqse9xe604qu2imv6rsjnhmn https://status.sirvoy.com/incident/cmqse9xe604qu2imv6rsjnhmn Booking.com Booking Retrieval Outage Type: Incident Duration: 1 hour and 25 minutes Affected Components: Booking.com Jun 22, 19:30: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. Jun 22, 20:55: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: 1 hour and 25 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>19:30: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>Jun <var data-var='date'> 22</var>, <var data-var='time'>20:55: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> ]]> Mon, 22 Jun 2026 19:30:00 +0000 https://status.sirvoy.com/incident/cmqpn5ocx00qy2oubbc016i9f https://status.sirvoy.com/incident/cmqpn5ocx00qy2oubbc016i9f Sirvoy Vault Issue Type: Incident Duration: 49 minutes Affected Components: Sirvoy Vault Jun 18, 15:14:00 GMT+0 - Identified - An issue at a third-party provider is currently causing our "Sirvoy Vault" feature not to work as expected. It causes you not to be able to view already saved CC details on the "Booking" view in Sirvoy. However, you can still manually add new CC details to bookings, and CC details for bookings originating from channels will still be added. We are sorry for the inconvenience. Please contact us at support@sirvoy.com if you have any questions regarding this. Jun 18, 16:03:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 49 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>15:14:00</var> GMT+0</small><br><strong>Identified</strong> - An issue at a third-party provider is currently causing our "Sirvoy Vault" feature not to work as expected. It causes you not to be able to view already saved CC details on the "Booking" view in Sirvoy. However, you can still manually add new CC details to bookings, and CC details for bookings originating from channels will still be added. We are sorry for the inconvenience. Please contact us at support@sirvoy.com if you have any questions regarding this..</p> <p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>16:03:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 18 Jun 2026 15:14:00 +0000 https://status.sirvoy.com/incident/cmqjo2g8w0hso2oml7mwea2wj https://status.sirvoy.com/incident/cmqjo2g8w0hso2oml7mwea2wj Security notice: phishing emails impersonating Sirvoy Type: Incident Duration: 4 days, 2 hours and 9 minutes Affected Components: Security Jun 15, 08:50:12 GMT+0 - Investigating - We are aware that some users are receiving phishing emails impersonating Sirvoy. These emails may contain suspicious links or lead to fake login pages designed to look like Sirvoy. Please be careful with unexpected emails claiming to be from Sirvoy. Do **not** click suspicious links, open unexpected attachments, or enter your login details unless you are sure the message is legitimate. If you are unsure, contact Sirvoy Support and we will help verify it. Always log in to Sirvoy directly at: [**secured.sirvoy.com**](http://secured.sirvoy.com) As a precaution, please check your recent account activity in Sirvoy under: **Settings > Users > Your activity** or **User Profile > Your Activity** If you see activity you do not recognize, or if you entered your login details through a suspicious email, please change the passwords for both your **Sirvoy account** and the **email account connected to your Sirvoy login**. Then contact Sirvoy Support so we can help review the account. Our team is actively investigating the reports. Jun 19, 10:59:30 GMT+0 - Resolved - Type: Incident

Duration: 4 days, 2 hours and 9 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>08:50:12</var> GMT+0</small><br><strong>Investigating</strong> - We are aware that some users are receiving phishing emails impersonating Sirvoy. These emails may contain suspicious links or lead to fake login pages designed to look like Sirvoy. Please be careful with unexpected emails claiming to be from Sirvoy. Do **not** click suspicious links, open unexpected attachments, or enter your login details unless you are sure the message is legitimate. If you are unsure, contact Sirvoy Support and we will help verify it. Always log in to Sirvoy directly at: [**secured.sirvoy.com**](http://secured.sirvoy.com) As a precaution, please check your recent account activity in Sirvoy under: **Settings > Users > Your activity** or **User Profile > Your Activity** If you see activity you do not recognize, or if you entered your login details through a suspicious email, please change the passwords for both your **Sirvoy account** and the **email account connected to your Sirvoy login**. Then contact Sirvoy Support so we can help review the account. Our team is actively investigating the reports..</p> <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>10:59:30</var> GMT+0</small><br><strong>Resolved</strong> - .</p> ]]> Mon, 15 Jun 2026 08:50:12 +0000 https://status.sirvoy.com/incident/cmqez36y6077s2jnz4rlurnse https://status.sirvoy.com/incident/cmqez36y6077s2jnz4rlurnse 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 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