Sirvoy Status - Incident history https://status.sirvoy.com Sirvoy Sun, 29 Mar 2026 02:45:00 +0000 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 Booking.com Booking Retrieval Outage Type: Incident Duration: 44 minutes Feb 11, 13: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. Feb 11, 14:30: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: 44 minutes

<p><small>Feb <var data-var='date'> 11</var>, <var data-var='time'>13: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>Feb <var data-var='date'> 11</var>, <var data-var='time'>14:30: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 Feb 2026 13:45:00 +0000 https://status.sirvoy.com/incident/cmli3aek000p8hh8468ysjvge https://status.sirvoy.com/incident/cmli3aek000p8hh8468ysjvge Booking.com Booking Retrieval Outage Type: Incident Duration: 1 hour and 3 minutes Affected Components: Booking.com Feb 11, 12: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. Feb 11, 13:13: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 3 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 11</var>, <var data-var='time'>12: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>Feb <var data-var='date'> 11</var>, <var data-var='time'>13:13: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 Feb 2026 12:10:00 +0000 https://status.sirvoy.com/incident/cmli04g5304mcxo9cenk4xw9i https://status.sirvoy.com/incident/cmli04g5304mcxo9cenk4xw9i Sirvoy Vault Issue Type: Incident Duration: 1 hour and 42 minutes Feb 3, 17:15:00 GMT+0 - Resolved - This incident has been resolved. Feb 3, 15:15: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. Type: Incident

Duration: 1 hour and 42 minutes

<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>17:15:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>15:15: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> ]]> Tue, 3 Feb 2026 15:15:00 +0000 https://status.sirvoy.com/incident/cml6v0b7708kxh0phz72t2vs3 https://status.sirvoy.com/incident/cml6v0b7708kxh0phz72t2vs3 Booking.com Booking Retrieval Outage Type: Incident Duration: 5 hours and 10 minutes Affected Components: Booking.com Jan 30, 11: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. Jan 30, 16:45: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: 5 hours and 10 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 30</var>, <var data-var='time'>11: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> <p><small>Jan <var data-var='date'> 30</var>, <var data-var='time'>16:45: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, 30 Jan 2026 11:35:00 +0000 https://status.sirvoy.com/incident/cmlgcmepf0a044ennqg7h6ycb https://status.sirvoy.com/incident/cmlgcmepf0a044ennqg7h6ycb Sirvoy Vault Issue Type: Incident Duration: 1 hour and 34 minutes Affected Components: Sirvoy Vault Jan 28, 16:12:00 GMT+0 - Resolved - During the time periods mentioned below, an issue at a third-party provider caused our "Sirvoy Vault" feature not to work as expected. You couldn't access saved CC details in the "Booking" view as a consequence of this problem. The possibility to add CC details manually and the saving of CC details for bookings originating from channels were not affected. The issue has now been resolved. We are sorry for the inconvenience. Please contact us at support@sirvoy.com if you have any questions regarding this. Jan 28, 14:38: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. Type: Incident

Duration: 1 hour and 34 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>16:12:00</var> GMT+0</small><br><strong>Resolved</strong> - During the time periods mentioned below, an issue at a third-party provider caused our "Sirvoy Vault" feature not to work as expected. You couldn't access saved CC details in the "Booking" view as a consequence of this problem. The possibility to add CC details manually and the saving of CC details for bookings originating from channels were not affected. The issue has now been resolved. We are sorry for the inconvenience. Please contact us at support@sirvoy.com if you have any questions regarding this..</p> <p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>14:38: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> ]]> Wed, 28 Jan 2026 14:38:00 +0000 https://status.sirvoy.com/incident/cmky6hqdk0hxwytjobhqjczz5 https://status.sirvoy.com/incident/cmky6hqdk0hxwytjobhqjczz5 Hostelworld Booking Retrieval Outage Type: Incident Duration: 1 hour Affected Components: Hostelworld Jan 21, 09:40:00 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. Jan 21, 10:40: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: 1 hour

Affected Components:

<p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>09:40:00</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>Jan <var data-var='date'> 21</var>, <var data-var='time'>10:40: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, 21 Jan 2026 09:40:00 +0000 https://status.sirvoy.com/incident/cmknvd7t013pz4liiwu3cqvaj https://status.sirvoy.com/incident/cmknvd7t013pz4liiwu3cqvaj Hostelworld Availability/Prices Updates Outage Type: Incident Duration: 49 minutes Jan 21, 09:37:00 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. Jan 21, 11: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: 49 minutes

<p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>09:37:00</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>Jan <var data-var='date'> 21</var>, <var data-var='time'>11: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, 21 Jan 2026 09:37:00 +0000 https://status.sirvoy.com/incident/cmknvb0dz09mvfzzyj0pvmd0x https://status.sirvoy.com/incident/cmknvb0dz09mvfzzyj0pvmd0x Booking.com Booking Retrieval Outage Type: Incident Duration: 7 minutes Jan 19, 15:51: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. Jan 19, 15:58: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: 7 minutes

<p><small>Jan <var data-var='date'> 19</var>, <var data-var='time'>15:51: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>Jan <var data-var='date'> 19</var>, <var data-var='time'>15:58: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, 19 Jan 2026 15:51:00 +0000 https://status.sirvoy.com/incident/cmkmuisxo01qjb91k2rekenkp https://status.sirvoy.com/incident/cmkmuisxo01qjb91k2rekenkp Hostelworld Booking Retrieval Outage Type: Incident Duration: 40 minutes Affected Components: Hostelworld Jan 15, 08:45:00 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. Jan 15, 09: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: 40 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>08:45:00</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>Jan <var data-var='date'> 15</var>, <var data-var='time'>09: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> ]]> Thu, 15 Jan 2026 08:45:00 +0000 https://status.sirvoy.com/incident/cmkf92tir002toq72bnqubojw https://status.sirvoy.com/incident/cmkf92tir002toq72bnqubojw Hostelworld Availability/Prices Updates Outage Type: Incident Duration: 1 hour and 10 minutes Affected Components: Hostelworld Jan 15, 08:28:00 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. Jan 15, 09:38: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: 1 hour and 10 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>08:28:00</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>Jan <var data-var='date'> 15</var>, <var data-var='time'>09:38: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> ]]> Thu, 15 Jan 2026 08:28:00 +0000 https://status.sirvoy.com/incident/cmkf8zskf0038n141zocx9l53 https://status.sirvoy.com/incident/cmkf8zskf0038n141zocx9l53 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