Incidents reported on status page for Streamline https://status.streamlinevrs.com/ https://d1lppblt9t2x15.cloudfront.net/logos/8175510fcb76da995c88b04b177e2a56.png https://status.streamlinevrs.com/ en https://status.streamlinevrs.com/ Tue, 13 Jan 2026 01:38:29 +0000 https://status.streamlinevrs.com/#980168004bd07da5e2d74b6b9dcb5067964efd0f2835f4aa7c32f78d970c0376 Streamline recovered https://status.streamlinevrs.com/ Tue, 13 Jan 2026 01:38:23 +0000 https://status.streamlinevrs.com/#b4d918a209004731e7e8bde0ffd0512ded172b493972a591e14c3514d6d12acc Streamline API recovered https://status.streamlinevrs.com/ Tue, 13 Jan 2026 01:20:55 +0000 https://status.streamlinevrs.com/#b4d918a209004731e7e8bde0ffd0512ded172b493972a591e14c3514d6d12acc Streamline API went down https://status.streamlinevrs.com/ Tue, 13 Jan 2026 01:19:29 +0000 https://status.streamlinevrs.com/#980168004bd07da5e2d74b6b9dcb5067964efd0f2835f4aa7c32f78d970c0376 Streamline went down https://status.streamlinevrs.com/ Tue, 18 Nov 2025 12:11:17 +0000 https://status.streamlinevrs.com/#c6ad2a17562800adbce96aeaec1b327ec69d5a5e8aef0d7fc9030d679d2800c5 Property Care recovered https://status.streamlinevrs.com/ Tue, 18 Nov 2025 11:56:05 +0000 https://status.streamlinevrs.com/#079bb4337ade723b338389a0f03c970a39bca25aea22ad93f826cfa4c75ce0db Streamline recovered https://status.streamlinevrs.com/ Tue, 18 Nov 2025 11:43:20 +0000 https://status.streamlinevrs.com/#079bb4337ade723b338389a0f03c970a39bca25aea22ad93f826cfa4c75ce0db Streamline went down https://status.streamlinevrs.com/ Tue, 18 Nov 2025 11:42:28 +0000 https://status.streamlinevrs.com/#c6ad2a17562800adbce96aeaec1b327ec69d5a5e8aef0d7fc9030d679d2800c5 Property Care went down https://status.streamlinevrs.com/ Tue, 18 Nov 2025 11:38:14 +0000 https://status.streamlinevrs.com/#c636487e049358c9af03b7497fd5017ffb3e8b9bd532913c3dc58725a7c2c8dd Owner X recovered https://status.streamlinevrs.com/ Tue, 18 Nov 2025 11:32:29 +0000 https://status.streamlinevrs.com/#c636487e049358c9af03b7497fd5017ffb3e8b9bd532913c3dc58725a7c2c8dd Owner X went down https://status.streamlinevrs.com/ Sun, 29 Jun 2025 18:44:28 +0000 https://status.streamlinevrs.com/#851fe3b0acae3ebd6abbc398b6efd6ee45de259d42c1493207bf25c28df2921b Property Care recovered https://status.streamlinevrs.com/ Sun, 29 Jun 2025 18:43:39 +0000 https://status.streamlinevrs.com/#3afa2f4b3b90c3b4b55e35d7c21f2f20e6a97784975f85622b079b48567e5fdb Happy Stays recovered https://status.streamlinevrs.com/ Sun, 29 Jun 2025 18:43:39 +0000 https://status.streamlinevrs.com/#f3c5b9dd3533dc3de3b640b17bc4ce573205666fa4e14553f93dc187bf5ca2b4 Owner X recovered https://status.streamlinevrs.com/ Sun, 29 Jun 2025 18:37:52 +0000 https://status.streamlinevrs.com/#f3c5b9dd3533dc3de3b640b17bc4ce573205666fa4e14553f93dc187bf5ca2b4 Owner X went down https://status.streamlinevrs.com/ Sun, 29 Jun 2025 18:37:49 +0000 https://status.streamlinevrs.com/#3afa2f4b3b90c3b4b55e35d7c21f2f20e6a97784975f85622b079b48567e5fdb Happy Stays went down https://status.streamlinevrs.com/ Sun, 29 Jun 2025 18:37:43 +0000 https://status.streamlinevrs.com/#851fe3b0acae3ebd6abbc398b6efd6ee45de259d42c1493207bf25c28df2921b Property Care went down https://status.streamlinevrs.com/ Tue, 03 Jun 2025 18:25:20 +0000 https://status.streamlinevrs.com/#ad256b87846977def14f4a6b0ceb9cc680cb13ea2a6eb20bb5b68a5c0c15e2bb Streamline recovered https://status.streamlinevrs.com/ Tue, 03 Jun 2025 18:25:09 +0000 https://status.streamlinevrs.com/#8ff8cccce74011d0507324151d57a4d79bd4fac0649ffd95c50f78748c6b2640 Streamline API recovered https://status.streamlinevrs.com/ Tue, 03 Jun 2025 18:18:23 +0000 https://status.streamlinevrs.com/#8ff8cccce74011d0507324151d57a4d79bd4fac0649ffd95c50f78748c6b2640 Streamline API went down https://status.streamlinevrs.com/ Tue, 03 Jun 2025 18:17:20 +0000 https://status.streamlinevrs.com/#ad256b87846977def14f4a6b0ceb9cc680cb13ea2a6eb20bb5b68a5c0c15e2bb Streamline went down https://status.streamlinevrs.com/ Wed, 21 May 2025 22:47:00 +0000 https://status.streamlinevrs.com/#1b7db3a5b4b35f9e4cd1e3fbdc47fc110a1f52bb48eeb3f61b7a6eff50534e3a Streamline recovered https://status.streamlinevrs.com/ Wed, 21 May 2025 22:46:53 +0000 https://status.streamlinevrs.com/#29443621ce27598725521922aa36b3a397ee086517d41b02ca0ae094c5b5e445 Streamline API recovered https://status.streamlinevrs.com/ Wed, 21 May 2025 22:37:51 +0000 https://status.streamlinevrs.com/#29443621ce27598725521922aa36b3a397ee086517d41b02ca0ae094c5b5e445 Streamline API went down https://status.streamlinevrs.com/ Wed, 21 May 2025 22:37:02 +0000 https://status.streamlinevrs.com/#1b7db3a5b4b35f9e4cd1e3fbdc47fc110a1f52bb48eeb3f61b7a6eff50534e3a Streamline went down https://status.streamlinevrs.com/ Thu, 03 Apr 2025 14:40:27 +0000 https://status.streamlinevrs.com/#831adacb0f796b779239c0c3e04d11616f46b829a2e6f4978b197ea09d66847c Streamline API recovered https://status.streamlinevrs.com/ Thu, 03 Apr 2025 14:39:40 +0000 https://status.streamlinevrs.com/#1cdb369371b4d92a1cdefe26e9082504e2381bbfb93eec5baac15620283e4d3e Streamline recovered https://status.streamlinevrs.com/ Thu, 03 Apr 2025 14:21:24 +0000 https://status.streamlinevrs.com/#831adacb0f796b779239c0c3e04d11616f46b829a2e6f4978b197ea09d66847c Streamline API went down https://status.streamlinevrs.com/ Thu, 03 Apr 2025 14:20:34 +0000 https://status.streamlinevrs.com/#1cdb369371b4d92a1cdefe26e9082504e2381bbfb93eec5baac15620283e4d3e Streamline went down https://status.streamlinevrs.com/incident/203996 Thu, 04 May 2023 04:18:00 -0000 https://status.streamlinevrs.com/incident/203996#6426a9fb3438846fd02b0a1aa6f8d8868d720fb6394518fcd7e1c7a95124aeb7 Resolved https://status.streamlinevrs.com/incident/203996 Wed, 03 May 2023 23:00:00 -0000 https://status.streamlinevrs.com/incident/203996#974c549f40ead112685b674e737ff9f66102218001821e18adb330ebe4046ed0 # What happened today 1. IT merged mulitple updates specifically pertaining to the Airbnb connection at approximately 02:10 am. 2. Sometime in the mid morning it was reported by multiple clients who Headlines or Descriptions did not meet the new Character limits were deactivated on the platform. 3. IT was alerted to the situation and begain investigating. 4. We discovered the issue in a validation process and mergeded to production. 5. A mass update was pushed to all impacted listings a few hours after the incident. 5. The issue was declared resolved at approximately 8:10 pm. # Why this happened 1. The issue was NOT the enforcement of Airbnb new character limit rule. 2. A code update temporarily caused an unwanted result with units getting delisted if their headline/description was out of validation with Airbnb for a new API version we updated to. 3. We merged logic for fall back conditions and this was an unexpected error. The intention was to not cause the delisting of units with this update and to prevent anyone from needing to make any updates to content that was grandfathered into Airbnb’s previous headline/description requirements. # Estimated costs 1. The situation lasted approximately ~16 hour. 2. 17,000 / 40,000 units were affected across multiple clients. # How to prevent this in the future Despite our best efforts to achieve perfection, there will inevitably be some errors that go unnoticed. We make a conscious effort to ensure that our work is of the highest quality by extensively testing our code and identifying as many bugs as possible prior to deploying it to production. We recognize that we can improve our response time and keep our clients informed by providing timely updates regarding any issues that arise and the steps we are taking to address them. https://status.streamlinevrs.com/incident/203993 Wed, 03 May 2023 22:55:00 -0000 https://status.streamlinevrs.com/incident/203993#452a84d4a7e494974372e672570cfaf9e9f3583d552385b08dc76b5ccf2ca9cf Everything has been resolved https://status.streamlinevrs.com/incident/203993 Wed, 03 May 2023 22:38:00 -0000 https://status.streamlinevrs.com/incident/203993#da85c440897a9bff20ea19b4ed1ee0bbc0cb21871e3de87b6baa5a9bd36036d1 # What happened today 1. IT merged a HotFix ticket to product at approximately 11:20 am 2. Shortly after it was reported that a Error 500 was being recieved when trying to create a reservation. 3. IT was alerted to the situation and begain investigating. 4. The issue was found and the code to fix it was put into place. 5. At approximately 12:30 pm the fix was merged to production. # Why this happened 1. We have specific steps that should be followed before any development task is merged to production. In this case, some of the steps for testing were missed. # Estimated costs 1. The situation lasted approximately ~1 hour and 30 minutes. 2. All clients were affected. # How to prevent this in the future 1. We are putting into place a verification process to make sure that each step of our process is strictly followed. We believe that adherence to each step in this case, would have caught the error prior to the functionality being released.