Incidents reported on status page for BL.INK https://status.bl.ink/ https://d1lppblt9t2x15.cloudfront.net/logos/0366264dc4c134f1fcf4f576f201ab3f.png https://status.bl.ink/ en https://status.bl.ink/ Tue, 11 Mar 2025 13:14:13 +0000 https://status.bl.ink/#12207da41c9e0919647358f4786e4f4a1cd76541a7e4be280e11a1e32e3b8d4e BLINK Website recovered https://status.bl.ink/ Tue, 11 Mar 2025 12:16:12 +0000 https://status.bl.ink/#12207da41c9e0919647358f4786e4f4a1cd76541a7e4be280e11a1e32e3b8d4e BLINK Website went down https://status.bl.ink/incident/518768 Sat, 01 Mar 2025 03:00:00 +0000 https://status.bl.ink/incident/518768#bd7be825964a257ddede9f5cb0ebebaae40809ca9bd1474fc9c50fdf003907df Maintenance completed https://status.bl.ink/incident/518768 Sat, 01 Mar 2025 03:00:00 +0000 https://status.bl.ink/incident/518768#bd7be825964a257ddede9f5cb0ebebaae40809ca9bd1474fc9c50fdf003907df Maintenance completed https://status.bl.ink/incident/518768 Sat, 01 Mar 2025 02:00:00 -0000 https://status.bl.ink/incident/518768#8c6d0ccb96ac16cc57019328be3246834821c97a4e86f01f4bf3d52d545828c7 WHEN Friday, February 28th, 2025 | 9:00pm - 10:00pm ET Saturday, March 1st, 2025 | 2:00am - 3:00am GMT Saturday, March 1st, 2025 | 10:00am - 11:00am SGT WHAT Routine maintenance is scheduled for Friday, February 28th, 2025 from 9:00pm - 10:00pm ET. This maintenance will include proactive patching and performance improvements for multiple core production services across the entire BLINK platform. IMPACT No downtime for production services is anticipated. However, there may be a brief period (less than a minute) where link redirects and API services could experience partial degradation. This update will apply to both Blink Enterprise and Self-Service customers. For any questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/518768 Sat, 01 Mar 2025 02:00:00 -0000 https://status.bl.ink/incident/518768#8c6d0ccb96ac16cc57019328be3246834821c97a4e86f01f4bf3d52d545828c7 WHEN Friday, February 28th, 2025 | 9:00pm - 10:00pm ET Saturday, March 1st, 2025 | 2:00am - 3:00am GMT Saturday, March 1st, 2025 | 10:00am - 11:00am SGT WHAT Routine maintenance is scheduled for Friday, February 28th, 2025 from 9:00pm - 10:00pm ET. This maintenance will include proactive patching and performance improvements for multiple core production services across the entire BLINK platform. IMPACT No downtime for production services is anticipated. However, there may be a brief period (less than a minute) where link redirects and API services could experience partial degradation. This update will apply to both Blink Enterprise and Self-Service customers. For any questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/ Wed, 29 Jan 2025 20:43:04 +0000 https://status.bl.ink/#23ee97851125b73ab99566405c6c91da884e669f7a3c86fa8fc939e5b4f61124 BL.INK Core Platform recovered https://status.bl.ink/ Wed, 29 Jan 2025 20:04:03 +0000 https://status.bl.ink/#23ee97851125b73ab99566405c6c91da884e669f7a3c86fa8fc939e5b4f61124 BL.INK Core Platform went down https://status.bl.ink/ Wed, 08 Jan 2025 18:24:45 +0000 https://status.bl.ink/#09dc9a799288aa78a3e6ef706fbb9e6284954229a43d81b09c493c5c09ee136b BL.INK Enterprise: USA recovered https://status.bl.ink/ Wed, 08 Jan 2025 18:13:43 +0000 https://status.bl.ink/#09dc9a799288aa78a3e6ef706fbb9e6284954229a43d81b09c493c5c09ee136b BL.INK Enterprise: USA went down https://status.bl.ink/incident/392179 Mon, 08 Jul 2024 03:00:00 +0000 https://status.bl.ink/incident/392179#327a8c04524a72a78cf986107d34486689b6889237112b9cc1593d145af618a7 Maintenance completed https://status.bl.ink/incident/392179 Mon, 08 Jul 2024 02:00:00 -0000 https://status.bl.ink/incident/392179#b447e41cbbac328962201db22554b181dda8b2ceed224f8197bf66c2d386fa1e We are performing maintenance impacting tenants on Cluster 2 of the BLINK V1 platform. This maintenance has been communicated in advance to account administrators via email. The maintenance will last approximately one hour with service-impacting activities taking up to 15 minutes during this timeframe. If you have any additional questions or concerns, please email help@bl.ink https://status.bl.ink/incident/392178 Sat, 06 Jul 2024 03:00:00 +0000 https://status.bl.ink/incident/392178#861c0c41900b137c73dd3140f17b87c0b8f2e86b6996131daec4d8d2b2ba6e65 Maintenance completed https://status.bl.ink/incident/392178 Sat, 06 Jul 2024 02:00:00 -0000 https://status.bl.ink/incident/392178#389d5e38df5453c995a4e5e5c1720a6e91ce955fa74bce5ca8b1c4c3e016f250 We are performing maintenance impacting tenants on Cluster 1 of the BLINK V1 platform. This maintenance has been communicated in advance to account administrators via email. The maintenance will last approximately one hour with service-impacting activities taking up to 15 minutes during this timeframe. If you have any additional questions or concerns, please email help@bl.ink https://status.bl.ink/incident/392177 Thu, 04 Jul 2024 03:00:00 +0000 https://status.bl.ink/incident/392177#54ebf497c4af1eff060a3937a89abe6f0a29e3baec5ec34b48a0dde044918db5 Maintenance completed https://status.bl.ink/incident/392177 Thu, 04 Jul 2024 02:00:00 -0000 https://status.bl.ink/incident/392177#95aab123c0471d72d0121d9cefed3bac427447643a1803b65ebc1da83ec29fc7 We are performing maintenance impacting tenants on Cluster 3 of the BLINK V1 platform. This maintenance has been communicated in advance to account administrators via email. The maintenance will last approximately one hour with service-impacting activities taking up to 15 minutes during this timeframe. If you have any additional questions or concerns, please email help@bl.ink https://status.bl.ink/incident/287206 Wed, 29 Nov 2023 09:00:00 +0000 https://status.bl.ink/incident/287206#6800814ede6ac85d4feca7fbd5dee6cd19674e5934ac2d3347998d7c4249e3ce Maintenance completed https://status.bl.ink/incident/287206 Wed, 29 Nov 2023 09:00:00 +0000 https://status.bl.ink/incident/287206#6800814ede6ac85d4feca7fbd5dee6cd19674e5934ac2d3347998d7c4249e3ce Maintenance completed https://status.bl.ink/incident/287206 Wed, 29 Nov 2023 05:05:00 -0000 https://status.bl.ink/incident/287206#82ba801fd8be9a95aa4e89b533ff51106149963d471feff095808c86be034544 WHEN Tuesday, November 29th, 2023 | 12:05am - 04:00am ET WHAT Quarterly maintenance is scheduled for Thursday, November 29th, 2023 at 11/29/2023 | 12:05am - 4:00am ET. This is for routine maintenance and proactive patching for multiple core production services across the entire BLINK platform. IMPACT No downtime for production services is anticipated, however it is possible that service may be partially degraded for link redirects and API services for a very brief period of time (less than a minute). This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/287206 Wed, 29 Nov 2023 05:05:00 -0000 https://status.bl.ink/incident/287206#82ba801fd8be9a95aa4e89b533ff51106149963d471feff095808c86be034544 WHEN Tuesday, November 29th, 2023 | 12:05am - 04:00am ET WHAT Quarterly maintenance is scheduled for Thursday, November 29th, 2023 at 11/29/2023 | 12:05am - 4:00am ET. This is for routine maintenance and proactive patching for multiple core production services across the entire BLINK platform. IMPACT No downtime for production services is anticipated, however it is possible that service may be partially degraded for link redirects and API services for a very brief period of time (less than a minute). This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/287201 Fri, 17 Nov 2023 07:00:00 +0000 https://status.bl.ink/incident/287201#56c34e514f16b5b0477ad212ee842f1673e5ddae20976acbbbdd12062a90c9d1 Maintenance completed https://status.bl.ink/incident/287201 Fri, 17 Nov 2023 07:00:00 +0000 https://status.bl.ink/incident/287201#56c34e514f16b5b0477ad212ee842f1673e5ddae20976acbbbdd12062a90c9d1 Maintenance completed https://status.bl.ink/incident/287201 Fri, 17 Nov 2023 03:00:00 -0000 https://status.bl.ink/incident/287201#6d0b4dfaa44d6af65f1037e489b7f7d475a0d063e272ad8183ef2e8bad0995a9 WHEN Thursday, November 16, 2023 from 09:00pm to 1:00am CT (03:00 - 7:00 UTC) WHAT Quarterly maintenance is scheduled for Thursday, November 16th, 2023 at 9pm ET - 1:00am CT. This is for routine maintenance and proactive patching for multiple core production services across the entire BLINK platform. IMPACT No downtime for production services is anticipated, however it is possible that service may be partially degraded for link redirects and API services for a very brief period of time (less than a minute). This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/287201 Fri, 17 Nov 2023 03:00:00 -0000 https://status.bl.ink/incident/287201#6d0b4dfaa44d6af65f1037e489b7f7d475a0d063e272ad8183ef2e8bad0995a9 WHEN Thursday, November 16, 2023 from 09:00pm to 1:00am CT (03:00 - 7:00 UTC) WHAT Quarterly maintenance is scheduled for Thursday, November 16th, 2023 at 9pm ET - 1:00am CT. This is for routine maintenance and proactive patching for multiple core production services across the entire BLINK platform. IMPACT No downtime for production services is anticipated, however it is possible that service may be partially degraded for link redirects and API services for a very brief period of time (less than a minute). This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/280029 Mon, 30 Oct 2023 20:25:00 -0000 https://status.bl.ink/incident/280029#5a19adf929c532041ff07cf91607f1410aa8f34d7c2a4c8b744f8b43b49b3d61 Today, October 30th, 2023 at 4:06pm Eastern, Cloudflare suffered an outage that affected BLINK authentication and log-in pages. The BLINK API and recently authenticated users were not affected. The issue was resolved by Cloudflare. BLINK services have returned to normal. https://status.bl.ink/incident/280029 Mon, 30 Oct 2023 20:25:00 -0000 https://status.bl.ink/incident/280029#5a19adf929c532041ff07cf91607f1410aa8f34d7c2a4c8b744f8b43b49b3d61 Today, October 30th, 2023 at 4:06pm Eastern, Cloudflare suffered an outage that affected BLINK authentication and log-in pages. The BLINK API and recently authenticated users were not affected. The issue was resolved by Cloudflare. BLINK services have returned to normal. https://status.bl.ink/incident/280029 Mon, 30 Oct 2023 20:14:00 -0000 https://status.bl.ink/incident/280029#fee6a726248c1f5abed782631194196b5fee7e35e71b89173bf69e446d07764b At the moment, some customers may have difficulty logging into Blink admin functions. API functions are operating normally. Our team is actively investigating the incident and will update you with more details as we have them. https://status.bl.ink/incident/280029 Mon, 30 Oct 2023 20:14:00 -0000 https://status.bl.ink/incident/280029#fee6a726248c1f5abed782631194196b5fee7e35e71b89173bf69e446d07764b At the moment, some customers may have difficulty logging into Blink admin functions. API functions are operating normally. Our team is actively investigating the incident and will update you with more details as we have them. https://status.bl.ink/incident/271478 Sat, 14 Oct 2023 04:45:00 +0000 https://status.bl.ink/incident/271478#1deab7c08b31d109b7f1b7c05faefe82906098601a0865287c2e79c95b3665fb Maintenance completed https://status.bl.ink/incident/271478 Sat, 14 Oct 2023 04:00:00 -0000 https://status.bl.ink/incident/271478#6ad1d3912537c67452761b84dd616d7996edd88e29e48ea7c413d5d817dbff96 **WHEN** Friday, October 13th, 2023 11pm-11:45pm Central (04:00-04:45 UTC) **DURATION** Service disruption is expected to be less than 5 minutes in length. **WHAT** BLINK is performing a reboot of our database servers to address both standard operating system and configuration updates. These updates are critical to the security and safety of our systems to ensure maximum performance. If there are any questions or concerns regarding this update, the timing, or the impact, please reach out to us at help@bl.ink for additional details. https://status.bl.ink/incident/241011 Tue, 15 Aug 2023 08:00:00 +0000 https://status.bl.ink/incident/241011#61eee464a8c30c0e0d3040ca3a55fbfb67e52a38c636aa684c1a5d7f5a7ad3f0 Maintenance completed https://status.bl.ink/incident/241011 Tue, 15 Aug 2023 08:00:00 +0000 https://status.bl.ink/incident/241011#61eee464a8c30c0e0d3040ca3a55fbfb67e52a38c636aa684c1a5d7f5a7ad3f0 Maintenance completed https://status.bl.ink/incident/241011 Tue, 15 Aug 2023 04:05:00 -0000 https://status.bl.ink/incident/241011#b9a3b473cbd093dca19d32fcce6f8636806243a4cc9d45296e9fc89572ff3662 **WHEN** Saturday, August 14, 2023 11:05AM CST - August 15, 2023 3:00AM CST **DURATION** Service degradation is expected to be less than 5 minutes in length. **WHAT** BLINK is performing routine patching, operating system and infrastructure updates. These updates are critical to the security and safety of our systems to ensure maximum performance. No downtime is expected however please expect a possible 5-minute degradation during the restart. If there are any questions or concerns regarding this update, the timing, or the impact, please reach out to us at help@bl.ink for additional details. https://status.bl.ink/incident/241011 Tue, 15 Aug 2023 04:05:00 -0000 https://status.bl.ink/incident/241011#b9a3b473cbd093dca19d32fcce6f8636806243a4cc9d45296e9fc89572ff3662 **WHEN** Saturday, August 14, 2023 11:05AM CST - August 15, 2023 3:00AM CST **DURATION** Service degradation is expected to be less than 5 minutes in length. **WHAT** BLINK is performing routine patching, operating system and infrastructure updates. These updates are critical to the security and safety of our systems to ensure maximum performance. No downtime is expected however please expect a possible 5-minute degradation during the restart. If there are any questions or concerns regarding this update, the timing, or the impact, please reach out to us at help@bl.ink for additional details. https://status.bl.ink/incident/241007 Sun, 13 Aug 2023 04:30:00 +0000 https://status.bl.ink/incident/241007#ea66e94eb3d9468a537a422210160075cfc422bb165c7db1ea2a70e4d90975b3 Maintenance completed https://status.bl.ink/incident/241007 Sun, 13 Aug 2023 04:30:00 +0000 https://status.bl.ink/incident/241007#ea66e94eb3d9468a537a422210160075cfc422bb165c7db1ea2a70e4d90975b3 Maintenance completed https://status.bl.ink/incident/241007 Sun, 13 Aug 2023 00:30:00 -0000 https://status.bl.ink/incident/241007#c43491e89237b11ce37af3f501b9a5b5b8b90cc270dd31a7ea3123fcdef90c8c **WHEN** Saturday, August 12, 2023 6:30pm-10:30pm Central (11:30-03:30 UTC) **DURATION** Service degradation is expected to be less than 5 minutes in length. **WHAT** BLINK is performing routine patching, operating system and infrastructure updates. These updates are critical to the security and safety of our systems to ensure maximum performance. No downtime is expected however please anticipate a possible 5-minute degradation during the restart. If there are any questions or concerns regarding this update, the timing, or the impact, please reach out to us at help@bl.ink for additional details. https://status.bl.ink/incident/241007 Sun, 13 Aug 2023 00:30:00 -0000 https://status.bl.ink/incident/241007#c43491e89237b11ce37af3f501b9a5b5b8b90cc270dd31a7ea3123fcdef90c8c **WHEN** Saturday, August 12, 2023 6:30pm-10:30pm Central (11:30-03:30 UTC) **DURATION** Service degradation is expected to be less than 5 minutes in length. **WHAT** BLINK is performing routine patching, operating system and infrastructure updates. These updates are critical to the security and safety of our systems to ensure maximum performance. No downtime is expected however please anticipate a possible 5-minute degradation during the restart. If there are any questions or concerns regarding this update, the timing, or the impact, please reach out to us at help@bl.ink for additional details. https://status.bl.ink/incident/222759 Fri, 23 Jun 2023 04:00:00 +0000 https://status.bl.ink/incident/222759#c36edb549d62dd59448edb77ef9ba5abc913f877c94aaa3f457a6aff6f043de3 Maintenance completed https://status.bl.ink/incident/222759 Fri, 23 Jun 2023 04:00:00 +0000 https://status.bl.ink/incident/222759#c36edb549d62dd59448edb77ef9ba5abc913f877c94aaa3f457a6aff6f043de3 Maintenance completed https://status.bl.ink/incident/222759 Fri, 23 Jun 2023 03:00:00 -0000 https://status.bl.ink/incident/222759#0da2bf8d2a410111a385198d9b2e6d58fd9e2ccf4dee1be2809c49b8dabce2c5 **WHEN** Thursday, June 22, 2023 10pm-11pm Central (03:00-04:00 UTC) **DURATION** Service disruption is expected to be less than 5 minutes in length. **WHAT** BLINK is performing a platform update to our edge services to address both standard operating system and infrastructure updates. These updates are critical to the security and safety of our systems to ensure maximum performance. If there are any questions or concerns regarding this update, the timing, or the impact, please reach out to us at help@bl.ink for additional details. https://status.bl.ink/incident/222759 Fri, 23 Jun 2023 03:00:00 -0000 https://status.bl.ink/incident/222759#0da2bf8d2a410111a385198d9b2e6d58fd9e2ccf4dee1be2809c49b8dabce2c5 **WHEN** Thursday, June 22, 2023 10pm-11pm Central (03:00-04:00 UTC) **DURATION** Service disruption is expected to be less than 5 minutes in length. **WHAT** BLINK is performing a platform update to our edge services to address both standard operating system and infrastructure updates. These updates are critical to the security and safety of our systems to ensure maximum performance. If there are any questions or concerns regarding this update, the timing, or the impact, please reach out to us at help@bl.ink for additional details. https://status.bl.ink/incident/219708 Thu, 15 Jun 2023 00:08:00 -0000 https://status.bl.ink/incident/219708#d3560229bbe187519902c44cdde25bbe490d12d489e82f0fbadb0aae4d0968f8 ## Root Cause Analysis of outage on June 13, 2023 BLINK experienced an outage on June 13th from approximately 1:52PM to 2:20PM Central time. Impact Assessment: The functions impacted were primary redirect services, multiple API endpoints, and web console functions. This outage impacted both self-service and enterprise customers. Timeline: (All times central. GMT -5) 1:52pm - initial alerts notified of 502 Bad Gateway response 2:08pm - AWS confirmed issues identified in the US-East Region were impacting all lambda functions (which BLINK utilizes in numerous places) 2:17pm - BLINK modified our services to skip the lambda services and process all traffic through another technology. All services started to recover. 2:20pm - All alerts cleared and systems were fully operational again. 4:00pm - AWS indicated that services were restored, but backlogged. BLINK monitored the situation until we felt confident that lambda services were operational. 5:15pm - BLINK reintroduced lambda services back into production. No issues were encountered. Root Cause Identification: The issue stemmed from the lambda functions being used to serve redirects and API calls. BLINK utilizes lambda as a primary application layer in our platform. While BLINK does not depend exclusively on this service, the failover to bypass the lambda layer is manual and required engineer intervention to transition. Action Plan: BLINK has been actively building a new structured architecture over the last 10 months that will provide a fully-dispersed footprint that utilizes multiple regions with immediate, automatic failover. Customers already on this new platform were not impacted by the outage providing real-world validation of the new architecture. This system is active today and we are working to transition to this new infrastructure in the near future. BLINK will begin sharing more details about this update in the coming months. Any immediate questions may be directed to help@bl.ink https://status.bl.ink/incident/219708 Thu, 15 Jun 2023 00:08:00 -0000 https://status.bl.ink/incident/219708#d3560229bbe187519902c44cdde25bbe490d12d489e82f0fbadb0aae4d0968f8 ## Root Cause Analysis of outage on June 13, 2023 BLINK experienced an outage on June 13th from approximately 1:52PM to 2:20PM Central time. Impact Assessment: The functions impacted were primary redirect services, multiple API endpoints, and web console functions. This outage impacted both self-service and enterprise customers. Timeline: (All times central. GMT -5) 1:52pm - initial alerts notified of 502 Bad Gateway response 2:08pm - AWS confirmed issues identified in the US-East Region were impacting all lambda functions (which BLINK utilizes in numerous places) 2:17pm - BLINK modified our services to skip the lambda services and process all traffic through another technology. All services started to recover. 2:20pm - All alerts cleared and systems were fully operational again. 4:00pm - AWS indicated that services were restored, but backlogged. BLINK monitored the situation until we felt confident that lambda services were operational. 5:15pm - BLINK reintroduced lambda services back into production. No issues were encountered. Root Cause Identification: The issue stemmed from the lambda functions being used to serve redirects and API calls. BLINK utilizes lambda as a primary application layer in our platform. While BLINK does not depend exclusively on this service, the failover to bypass the lambda layer is manual and required engineer intervention to transition. Action Plan: BLINK has been actively building a new structured architecture over the last 10 months that will provide a fully-dispersed footprint that utilizes multiple regions with immediate, automatic failover. Customers already on this new platform were not impacted by the outage providing real-world validation of the new architecture. This system is active today and we are working to transition to this new infrastructure in the near future. BLINK will begin sharing more details about this update in the coming months. Any immediate questions may be directed to help@bl.ink https://status.bl.ink/incident/219708 Tue, 13 Jun 2023 20:00:00 -0000 https://status.bl.ink/incident/219708#d3305e529dd928a362e647bc6ff2c36b55ab10cd55a74990c32d7cba98aff328 AWS services appear to be operational again, however an official update has not yet been announced so we are still operating without the lambda services. All functions are operating normally and without issue. We are considering this outage Resolved at this time and will reintroduce Lambda services back into our stack once we are confident the issue has been resolved. There are no anticipated outages during the Lambda reactivation so a formal announcement will not be made. A root cause analysis of this issue will be posted within 24 hours with additional details. https://status.bl.ink/incident/219708 Tue, 13 Jun 2023 20:00:00 -0000 https://status.bl.ink/incident/219708#d3305e529dd928a362e647bc6ff2c36b55ab10cd55a74990c32d7cba98aff328 AWS services appear to be operational again, however an official update has not yet been announced so we are still operating without the lambda services. All functions are operating normally and without issue. We are considering this outage Resolved at this time and will reintroduce Lambda services back into our stack once we are confident the issue has been resolved. There are no anticipated outages during the Lambda reactivation so a formal announcement will not be made. A root cause analysis of this issue will be posted within 24 hours with additional details. https://status.bl.ink/incident/219708 Tue, 13 Jun 2023 19:25:00 -0000 https://status.bl.ink/incident/219708#a4b484bfd8ee26cf42d895be79b32688ba01c1b5dbd32b3497de30834900e327 We have identified the source of the outage and confirmed it is related to the AWS Lambda outage in the US-East region. We have reconfigured our systems to bypass the Lambda services and all functions appear to be restored. We are currently reviewing all systems to confirm operations. We will post another update by 3pm Central time with additional information. https://status.bl.ink/incident/219708 Tue, 13 Jun 2023 19:25:00 -0000 https://status.bl.ink/incident/219708#a4b484bfd8ee26cf42d895be79b32688ba01c1b5dbd32b3497de30834900e327 We have identified the source of the outage and confirmed it is related to the AWS Lambda outage in the US-East region. We have reconfigured our systems to bypass the Lambda services and all functions appear to be restored. We are currently reviewing all systems to confirm operations. We will post another update by 3pm Central time with additional information. https://status.bl.ink/incident/219708 Tue, 13 Jun 2023 19:05:00 -0000 https://status.bl.ink/incident/219708#84377e766e268b5f759622d398856ceacee5c65d40a92bb87f019bca2b23adab We are currently experiencing a service outage across redirects and management functions. We will post additional information as soon as it becomes available. https://status.bl.ink/incident/219708 Tue, 13 Jun 2023 19:05:00 -0000 https://status.bl.ink/incident/219708#84377e766e268b5f759622d398856ceacee5c65d40a92bb87f019bca2b23adab We are currently experiencing a service outage across redirects and management functions. We will post additional information as soon as it becomes available. https://status.bl.ink/incident/204960 Tue, 16 May 2023 09:00:00 +0000 https://status.bl.ink/incident/204960#a2f44f519527c0d068eaa33f74b03748de07591568f578d524a9329865758e23 Maintenance completed https://status.bl.ink/incident/204960 Tue, 16 May 2023 09:00:00 +0000 https://status.bl.ink/incident/204960#a2f44f519527c0d068eaa33f74b03748de07591568f578d524a9329865758e23 Maintenance completed https://status.bl.ink/incident/204960 Tue, 16 May 2023 04:00:00 -0000 https://status.bl.ink/incident/204960#2c5512b7f8538adc06a07e71ea392aaf4dd7e7f0a31a7b534dc160e2b98c2b37 WHEN: Tuesday, May 16, 2023 from 12:00PM EDT to 4:00AM - May 16, 2023 EDT (04:00 - 08:00 UTC) WHAT: Routine maintenance and proactive patching for our primary production services across the entire BLINK platform. IMPACT: No downtime for production services is anticipated. This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/204960 Tue, 16 May 2023 04:00:00 -0000 https://status.bl.ink/incident/204960#2c5512b7f8538adc06a07e71ea392aaf4dd7e7f0a31a7b534dc160e2b98c2b37 WHEN: Tuesday, May 16, 2023 from 12:00PM EDT to 4:00AM - May 16, 2023 EDT (04:00 - 08:00 UTC) WHAT: Routine maintenance and proactive patching for our primary production services across the entire BLINK platform. IMPACT: No downtime for production services is anticipated. This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/204965 Sun, 14 May 2023 03:30:00 +0000 https://status.bl.ink/incident/204965#ac05dc195b92886564abbc64da065444c41ab40df230908c2b8061d416038c36 Maintenance completed https://status.bl.ink/incident/204965 Sun, 14 May 2023 03:30:00 +0000 https://status.bl.ink/incident/204965#ac05dc195b92886564abbc64da065444c41ab40df230908c2b8061d416038c36 Maintenance completed https://status.bl.ink/incident/204965 Sat, 13 May 2023 23:30:00 -0000 https://status.bl.ink/incident/204965#0e445df1430698a43e7dfac306b30fbfef6f9531efbef4e6b388ce71726b982e WHEN: Saturday, May 13th, 2023 from 7:30PM to 11:30PM - May 13th, 2023 EDT (11:30PM – May 14th 03:30 UTC) WHAT: Routine maintenance and proactive patching for our primary production services across the entire BLINK platform. IMPACT: No downtime for production services is anticipated. This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/204965 Sat, 13 May 2023 23:30:00 -0000 https://status.bl.ink/incident/204965#0e445df1430698a43e7dfac306b30fbfef6f9531efbef4e6b388ce71726b982e WHEN: Saturday, May 13th, 2023 from 7:30PM to 11:30PM - May 13th, 2023 EDT (11:30PM – May 14th 03:30 UTC) WHAT: Routine maintenance and proactive patching for our primary production services across the entire BLINK platform. IMPACT: No downtime for production services is anticipated. This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/192585 Mon, 03 Apr 2023 22:20:00 +0000 https://status.bl.ink/incident/192585#f0f53becfa997b2d310d9093342357f027145d77b6f6d1dab2de92bb4d3d6631 Maintenance completed https://status.bl.ink/incident/192585 Mon, 03 Apr 2023 22:11:00 -0000 https://status.bl.ink/incident/192585#891705a997cd9f561ef1e6ecedf160879658dca6da81f59d91e8e49896ca895f Some BL.INK customers experienced a temporary interruption of service in the Amazon East Region. Our DevOps team initiated optimization routines that caused high CPU utilization in one of our databases. This issue caused reduced performance of our administration interface and our APIs for a subset of customers. The issue was resolved quickly by terminating the problematic maintenance queries. No data was lost and all services have been restored to their full capacity. Future maintenance will be scheduled outside of normal business hours to minimize any impact or degradation. https://status.bl.ink/incident/173597 Mon, 20 Feb 2023 21:00:00 +0000 https://status.bl.ink/incident/173597#53e3900947caf37ea63e1f054ba5230ca7a296135698205a5625957c93b7124b Maintenance completed https://status.bl.ink/incident/173597 Mon, 20 Feb 2023 21:00:00 +0000 https://status.bl.ink/incident/173597#53e3900947caf37ea63e1f054ba5230ca7a296135698205a5625957c93b7124b Maintenance completed https://status.bl.ink/incident/173597 Mon, 20 Feb 2023 06:01:00 -0000 https://status.bl.ink/incident/173597#58d4eb8f4a6d8454c47bec0a9a16f59e8bd4c1730c8a2d486855fe7b769980f4 REVISED DATE & TIME WHEN: Monday, February 20, 2023 from 12:01am to 3:00am - February 20, 2023 CST (06:00 - 09:00 UTC) WHAT: Routine maintenance and proactive patching for multiple secondary production services across the entire BLINK platform. IMPACT: No downtime for production services is anticipated.. This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/173597 Mon, 20 Feb 2023 06:01:00 -0000 https://status.bl.ink/incident/173597#58d4eb8f4a6d8454c47bec0a9a16f59e8bd4c1730c8a2d486855fe7b769980f4 REVISED DATE & TIME WHEN: Monday, February 20, 2023 from 12:01am to 3:00am - February 20, 2023 CST (06:00 - 09:00 UTC) WHAT: Routine maintenance and proactive patching for multiple secondary production services across the entire BLINK platform. IMPACT: No downtime for production services is anticipated.. This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/174895 Sat, 18 Feb 2023 12:00:00 +0000 https://status.bl.ink/incident/174895#e22c4c6ba60829c568cb2fe2829623b9415736b67382f480011c49c73fbb6fad Maintenance completed https://status.bl.ink/incident/174895 Sat, 18 Feb 2023 12:00:00 +0000 https://status.bl.ink/incident/174895#e22c4c6ba60829c568cb2fe2829623b9415736b67382f480011c49c73fbb6fad Maintenance completed https://status.bl.ink/incident/174895 Sat, 18 Feb 2023 08:00:00 -0000 https://status.bl.ink/incident/174895#bd4a3f8c80ab9a51861a81ae8ac5ccce0fe9a688091ac742c03dbf7b8d1e1504 WHEN Saturday, February 18, 2023 from 2:00am to 6:00am CST (08:00 - 12:00 UTC) WHAT The maintenance scheduled for Saturday, February 11th was incomplete, so another window has been scheduled to complete the maintenance. This is for routine maintenance and proactive patching for multiple core production services across the entire BLINK platform. IMPACT No downtime for production services is anticipated, however it is possible that service may be partially degraded for link redirects and API services for a very brief period of time (less than a minute). This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/174895 Sat, 18 Feb 2023 08:00:00 -0000 https://status.bl.ink/incident/174895#bd4a3f8c80ab9a51861a81ae8ac5ccce0fe9a688091ac742c03dbf7b8d1e1504 WHEN Saturday, February 18, 2023 from 2:00am to 6:00am CST (08:00 - 12:00 UTC) WHAT The maintenance scheduled for Saturday, February 11th was incomplete, so another window has been scheduled to complete the maintenance. This is for routine maintenance and proactive patching for multiple core production services across the entire BLINK platform. IMPACT No downtime for production services is anticipated, however it is possible that service may be partially degraded for link redirects and API services for a very brief period of time (less than a minute). This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/173595 Sun, 12 Feb 2023 04:30:00 +0000 https://status.bl.ink/incident/173595#cfb477a9d5b83af8a6d7e3051a11de901c83cd945f5e68628407cb5779f5cb4c Maintenance completed https://status.bl.ink/incident/173595 Sun, 12 Feb 2023 04:30:00 +0000 https://status.bl.ink/incident/173595#cfb477a9d5b83af8a6d7e3051a11de901c83cd945f5e68628407cb5779f5cb4c Maintenance completed https://status.bl.ink/incident/173595 Sun, 12 Feb 2023 00:30:00 -0000 https://status.bl.ink/incident/173595#a3beccfc59b49f8a153b378a2a1fe0bf34920d8666f6304d6b48656534c3d602 When Saturday, February 11, 2023 from 6:30pm to 10:30pm CST (00:30 - 05:00 UTC) What Routine maintenance and proactive patching for multiple core production services across the entire BLINK platform. Impact No downtime for production services is anticipated, however it is possible that service may be partially degraded for link redirects and API services for a very brief period of time (less than a minute). This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/173595 Sun, 12 Feb 2023 00:30:00 -0000 https://status.bl.ink/incident/173595#a3beccfc59b49f8a153b378a2a1fe0bf34920d8666f6304d6b48656534c3d602 When Saturday, February 11, 2023 from 6:30pm to 10:30pm CST (00:30 - 05:00 UTC) What Routine maintenance and proactive patching for multiple core production services across the entire BLINK platform. Impact No downtime for production services is anticipated, however it is possible that service may be partially degraded for link redirects and API services for a very brief period of time (less than a minute). This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/135164 Tue, 15 Nov 2022 09:00:00 +0000 https://status.bl.ink/incident/135164#f0e4040fa19bc1c96c0f62435c0ebe382c7b96df2b8600ca9235d5b625e9b4ee Maintenance completed https://status.bl.ink/incident/135164 Tue, 15 Nov 2022 09:00:00 +0000 https://status.bl.ink/incident/135164#f0e4040fa19bc1c96c0f62435c0ebe382c7b96df2b8600ca9235d5b625e9b4ee Maintenance completed https://status.bl.ink/incident/135164 Tue, 15 Nov 2022 05:00:00 -0000 https://status.bl.ink/incident/135164#9849c5a06fe681ea0833cd4b5827c8dd705bcd493b7fedd3772a4d1305843bce BLINK will be performing a second planned maintenance on our production environment for routine patching and updates to secondary systems. This is scheduled to take place on Monday, November 14th from 11:00pm-3:00am Central time (05:00-09:00 UTC). No downtime for production services is anticipated, however it is possible that service may be partially degraded for link redirects and/or API services for a very brief period of time (less than a minute). This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/135164 Tue, 15 Nov 2022 05:00:00 -0000 https://status.bl.ink/incident/135164#9849c5a06fe681ea0833cd4b5827c8dd705bcd493b7fedd3772a4d1305843bce BLINK will be performing a second planned maintenance on our production environment for routine patching and updates to secondary systems. This is scheduled to take place on Monday, November 14th from 11:00pm-3:00am Central time (05:00-09:00 UTC). No downtime for production services is anticipated, however it is possible that service may be partially degraded for link redirects and/or API services for a very brief period of time (less than a minute). This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/134822 Sun, 13 Nov 2022 04:30:00 +0000 https://status.bl.ink/incident/134822#e4e1901bb137599d23fcd42948d78e1b2d920e0d29636feb62aac3347701057a Maintenance completed https://status.bl.ink/incident/134822 Sun, 13 Nov 2022 04:30:00 +0000 https://status.bl.ink/incident/134822#e4e1901bb137599d23fcd42948d78e1b2d920e0d29636feb62aac3347701057a Maintenance completed https://status.bl.ink/incident/134822 Sun, 13 Nov 2022 00:30:00 -0000 https://status.bl.ink/incident/134822#0f97c4b059c510ec28b936c59b304fca248c16aa61c568c8f96468fc534e676a BLINK will be performing planned maintenance on our production environment for routine patching and updates. This is scheduled to take place on Saturday, November 12th from 6:30pm-10:30pm Central time (00:30-04:30 UTC). It is anticipated that a brief disruption (approximately a minute) may occur during this window as secondary services are engaged. This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/134822 Sun, 13 Nov 2022 00:30:00 -0000 https://status.bl.ink/incident/134822#0f97c4b059c510ec28b936c59b304fca248c16aa61c568c8f96468fc534e676a BLINK will be performing planned maintenance on our production environment for routine patching and updates. This is scheduled to take place on Saturday, November 12th from 6:30pm-10:30pm Central time (00:30-04:30 UTC). It is anticipated that a brief disruption (approximately a minute) may occur during this window as secondary services are engaged. This update will occur for both Enterprise and Self-Service customers. For questions regarding this update, please contact us at help@bl.ink. https://status.bl.ink/incident/106288 Sun, 07 Aug 2022 05:00:00 +0000 https://status.bl.ink/incident/106288#1e99ac010daabb6ba085618916c9f089b94bf6e17226dacbde38d3d08faad135 Maintenance completed https://status.bl.ink/incident/106288 Sun, 07 Aug 2022 05:00:00 +0000 https://status.bl.ink/incident/106288#1e99ac010daabb6ba085618916c9f089b94bf6e17226dacbde38d3d08faad135 Maintenance completed https://status.bl.ink/incident/106288 Sun, 07 Aug 2022 01:00:00 -0000 https://status.bl.ink/incident/106288#8b8ce88de703c701d1f9c6c4a948e0f6a82c5bb6a1f91e9c15a95ab4fae8c253 BLINK is scheduling our quarterly patching for all secondary servers on August 7 from 01:00 to 05:00 UTC. Due to the nature of some patches, a reboot or restart of a service may be required. The update only applies to secondary services so no disruption is expected. For any questions or concerns regarding these updates, please contact us at help@bl.ink https://status.bl.ink/incident/106288 Sun, 07 Aug 2022 01:00:00 -0000 https://status.bl.ink/incident/106288#8b8ce88de703c701d1f9c6c4a948e0f6a82c5bb6a1f91e9c15a95ab4fae8c253 BLINK is scheduling our quarterly patching for all secondary servers on August 7 from 01:00 to 05:00 UTC. Due to the nature of some patches, a reboot or restart of a service may be required. The update only applies to secondary services so no disruption is expected. For any questions or concerns regarding these updates, please contact us at help@bl.ink https://status.bl.ink/incident/105867 Sun, 31 Jul 2022 04:00:00 +0000 https://status.bl.ink/incident/105867#6d22f72dec5d84da95f09e6a742a9b237ca068be4c0dab7ddba00a65be5db2c8 Maintenance completed https://status.bl.ink/incident/105867 Sun, 31 Jul 2022 04:00:00 +0000 https://status.bl.ink/incident/105867#6d22f72dec5d84da95f09e6a742a9b237ca068be4c0dab7ddba00a65be5db2c8 Maintenance completed https://status.bl.ink/incident/105867 Sun, 31 Jul 2022 00:00:00 -0000 https://status.bl.ink/incident/105867#e7670008d15653a771f2d9c1399973318c5c0c87676e1e31222294c0a3e962a7 BLINK is scheduling our quarterly patching for all servers on July 31 from 00:00 to 04:00 UTC. Due to the nature of some patches, a reboot or restart of a service may be required. In these instances, our systems are designed to automatically fail over to backup systems to ensure continuity of service. Monitoring systems may trigger an alert as backup systems are actively receiving new traffic. Any disruption to specific services should be very brief (approximately 1 minute) and the updates will be started and completed within the specified window. For any questions or concerns regarding these updates, please contact us at help@bl.ink https://status.bl.ink/incident/105867 Sun, 31 Jul 2022 00:00:00 -0000 https://status.bl.ink/incident/105867#e7670008d15653a771f2d9c1399973318c5c0c87676e1e31222294c0a3e962a7 BLINK is scheduling our quarterly patching for all servers on July 31 from 00:00 to 04:00 UTC. Due to the nature of some patches, a reboot or restart of a service may be required. In these instances, our systems are designed to automatically fail over to backup systems to ensure continuity of service. Monitoring systems may trigger an alert as backup systems are actively receiving new traffic. Any disruption to specific services should be very brief (approximately 1 minute) and the updates will be started and completed within the specified window. For any questions or concerns regarding these updates, please contact us at help@bl.ink https://status.bl.ink/incident/85460 Sat, 07 May 2022 02:58:46 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Sat, 07 May 2022 02:58:46 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Fri, 06 May 2022 20:00:00 +0000 https://status.bl.ink/incident/85460#f903b1c68e473da980ddb829f9f956dca9b44a56d09a2fb29c9dcc5a5248bdb6 Maintenance completed https://status.bl.ink/incident/85460 Fri, 06 May 2022 20:00:00 +0000 https://status.bl.ink/incident/85460#f903b1c68e473da980ddb829f9f956dca9b44a56d09a2fb29c9dcc5a5248bdb6 Maintenance completed https://status.bl.ink/incident/85460 Fri, 06 May 2022 18:37:57 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Fri, 06 May 2022 18:37:57 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Fri, 06 May 2022 01:42:54 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Fri, 06 May 2022 01:42:54 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Wed, 04 May 2022 22:56:18 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Wed, 04 May 2022 22:56:18 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Wed, 04 May 2022 20:10:10 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Wed, 04 May 2022 20:10:10 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Wed, 04 May 2022 16:34:05 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Wed, 04 May 2022 16:34:05 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Wed, 04 May 2022 15:25:48 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Wed, 04 May 2022 15:25:48 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Wed, 04 May 2022 15:00:00 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/85460 Wed, 04 May 2022 15:00:00 -0000 https://status.bl.ink/incident/85460#74529bfc80c93d5f07d491bab885468b655d2a8cf1e75aa73a744009e2199d4d BLINK is planning a non-disruptive update scheduled for Tuesday, May 4th between 10am-3pm (15:00 - 20:00 UTC). BLINK has tested the update extensively, however due to the significance of the update across multiple internal systems, we are notifying our customers in advance to reach out to us at help@bl.ink if you see any anomalies in your operations. All redirects, API, and management console should experience zero disruption during the update. We will provide additional notifications during the maintenance and at the conclusion. NOTE: this maintenance was originally scheduled for May 3rd, however our team felt another day was warranted to finalize some preparations to ensure a smooth and seamless transition. https://status.bl.ink/incident/78482 Mon, 28 Mar 2022 14:31:00 -0000 https://status.bl.ink/incident/78482#90a29c5e18807ed02240e7f4701aefe54fb8354610d6a8dba9c09fb9fef882e3 During a configuration update of our monitoring systems, we inadvertently triggered an alarm status signaling an outage. All services were online 100% during this time and there was no actual outage. This alert was triggered by a misconfiguration of our monitoring services. For any additional questions, please contact our helpdesk. Thank You! https://status.bl.ink/incident/78482 Mon, 28 Mar 2022 14:31:00 -0000 https://status.bl.ink/incident/78482#90a29c5e18807ed02240e7f4701aefe54fb8354610d6a8dba9c09fb9fef882e3 During a configuration update of our monitoring systems, we inadvertently triggered an alarm status signaling an outage. All services were online 100% during this time and there was no actual outage. This alert was triggered by a misconfiguration of our monitoring services. For any additional questions, please contact our helpdesk. Thank You! https://status.bl.ink/incident/63384 Wed, 22 Dec 2021 12:57:00 -0000 https://status.bl.ink/incident/63384#d6f59bf6181488b49b3b5e836d9e59db619989acd5fa453fd5e6698b6983e0b1 An AWS outage is currently impacting our primary edge endpoint and due to the nature of the outage, failover protocols were unresponsive. Our team has manually failed services to our secondary cluster and services are now restored. We will continue to monitor the situation at AWS and report here with any additional updates. https://status.bl.ink/incident/63384 Wed, 22 Dec 2021 12:23:00 -0000 https://status.bl.ink/incident/63384#92a4acdca3f615f0387692e21a05eb197a540379a6c6b404f178c7418b9c5bf0 BLINK is aware of a service disruption impacting some enterprise customers access to the console and redirect services. We are actively investigating and will update the status here soon. https://status.bl.ink/incident/62573 Wed, 15 Dec 2021 16:01:00 -0000 https://status.bl.ink/incident/62573#fe520b4cafd7cc3ddf11c368b147e57e581c0dcdb07f53e7609036a9cd3dda25 Authentication services are now operating again. Your experience may be a bit slower than normal, but we are no longer experiencing any errors and seeing steady improvement across all authentication sessions. We will continue to monitor the situation at Auth0. If you are experiencing any ongoing issues, please contact us. https://status.bl.ink/incident/62573 Wed, 15 Dec 2021 16:01:00 -0000 https://status.bl.ink/incident/62573#fe520b4cafd7cc3ddf11c368b147e57e581c0dcdb07f53e7609036a9cd3dda25 Authentication services are now operating again. Your experience may be a bit slower than normal, but we are no longer experiencing any errors and seeing steady improvement across all authentication sessions. We will continue to monitor the situation at Auth0. If you are experiencing any ongoing issues, please contact us. https://status.bl.ink/incident/62573 Wed, 15 Dec 2021 15:50:00 -0000 https://status.bl.ink/incident/62573#27908e3e652714f606624c95c1c9b37cca269fa48f05ef00a0019c3ae8ce778a Our authentication provider, Auth0, has reported degraded services that are causing issues for new authentication requests. Users that are already authenticated may use BLINK without issue, however any new requests to authenticate during login appear to be failing. We are continuing to monitor the situation and will share updates as they are available. Auth0 Status Page: https://status.auth0.com https://status.bl.ink/incident/62573 Wed, 15 Dec 2021 15:50:00 -0000 https://status.bl.ink/incident/62573#27908e3e652714f606624c95c1c9b37cca269fa48f05ef00a0019c3ae8ce778a Our authentication provider, Auth0, has reported degraded services that are causing issues for new authentication requests. Users that are already authenticated may use BLINK without issue, however any new requests to authenticate during login appear to be failing. We are continuing to monitor the situation and will share updates as they are available. Auth0 Status Page: https://status.auth0.com https://status.bl.ink/incident/61834 Tue, 14 Dec 2021 21:08:26 -0000 https://status.bl.ink/incident/61834#8350779618a3f4417bc49aaed74062dd283fe27aeb50b4d7ba8ba49223db61b0 We will be performing database maintenance that will impact the ability to create new links for up to 30 minutes. Existing links will redirect without issue. During the maintenance window, access to the control panel will be disabled and API requests to create or edit links will respond with an error. As soon as the maintenance is complete, all services will be restored. The process will occur between 2pm CST (20:00 UTC) and 3pm CST (21:00 UTC), however the actual impact should be 30 minutes or less. All existing links will function without issue. The limitation is only to create new or edit existing links. This maintenance applies to all self-service accounts who access BLINK at app.bl.ink. Enterprise customers impacted during this window have been notified separately. https://status.bl.ink/incident/61834 Tue, 14 Dec 2021 21:00:00 +0000 https://status.bl.ink/incident/61834#0e0779b2924e434d216c26f7eeae5a2e32f5f7b0d809ec8f1d0333151a2a7c2a Maintenance completed https://status.bl.ink/incident/61834 Tue, 14 Dec 2021 20:00:00 -0000 https://status.bl.ink/incident/61834#8350779618a3f4417bc49aaed74062dd283fe27aeb50b4d7ba8ba49223db61b0 We will be performing database maintenance that will impact the ability to create new links for up to 30 minutes. Existing links will redirect without issue. During the maintenance window, access to the control panel will be disabled and API requests to create or edit links will respond with an error. As soon as the maintenance is complete, all services will be restored. The process will occur between 2pm CST (20:00 UTC) and 3pm CST (21:00 UTC), however the actual impact should be 30 minutes or less. All existing links will function without issue. The limitation is only to create new or edit existing links. This maintenance applies to all self-service accounts who access BLINK at app.bl.ink. Enterprise customers impacted during this window have been notified separately. https://status.bl.ink/incident/61943 Fri, 10 Dec 2021 17:30:00 -0000 https://status.bl.ink/incident/61943#049dfade14215f4f4ab832a9783eb099506e84cdc2ce879ea5b0347886eab447 We have reverted the incorrect configuration and all services are operating again. We will be reviewing our runbooks to ensure we avoid these situations moving forward. Our apologies for the disruption and appreciation for your understanding. https://status.bl.ink/incident/61943 Fri, 10 Dec 2021 17:30:00 -0000 https://status.bl.ink/incident/61943#049dfade14215f4f4ab832a9783eb099506e84cdc2ce879ea5b0347886eab447 We have reverted the incorrect configuration and all services are operating again. We will be reviewing our runbooks to ensure we avoid these situations moving forward. Our apologies for the disruption and appreciation for your understanding. https://status.bl.ink/incident/61943 Fri, 10 Dec 2021 17:26:00 -0000 https://status.bl.ink/incident/61943#87bc261c48236410ac97b7ecadf913f6eb17ae742af6b58aac68bbbf51d5dcbb While performing an optimization change, an engineer introduced an incorrect configuration which is rendering a 502 Bad Gateway for some redirection requests. We are reverting the change now and full service should be restored momentarily. The web console and API are not impacted. https://status.bl.ink/incident/61943 Fri, 10 Dec 2021 17:26:00 -0000 https://status.bl.ink/incident/61943#87bc261c48236410ac97b7ecadf913f6eb17ae742af6b58aac68bbbf51d5dcbb While performing an optimization change, an engineer introduced an incorrect configuration which is rendering a 502 Bad Gateway for some redirection requests. We are reverting the change now and full service should be restored momentarily. The web console and API are not impacted. https://status.bl.ink/incident/61825 Thu, 09 Dec 2021 17:18:00 -0000 https://status.bl.ink/incident/61825#49abc7fb6ec5c3c4c79751076f2657b16cf88ea6b08bd1f84bac7a4e6cc22300 Services are fully online again without issue. We will continue to monitor all services to ensure everything is operating as expected and will begin our root cause analysis of the issue. https://status.bl.ink/incident/61825 Thu, 09 Dec 2021 17:18:00 -0000 https://status.bl.ink/incident/61825#49abc7fb6ec5c3c4c79751076f2657b16cf88ea6b08bd1f84bac7a4e6cc22300 Services are fully online again without issue. We will continue to monitor all services to ensure everything is operating as expected and will begin our root cause analysis of the issue. https://status.bl.ink/incident/61825 Thu, 09 Dec 2021 17:13:00 -0000 https://status.bl.ink/incident/61825#3581ccbc4b507fcb640ba11e8edcf6b40d4e081b5984a9621ae38ad96c5899df An application error has been returned across some services across some customer sites. We are investigating. Sites are currently online again, but we are researching the root cause. https://status.bl.ink/incident/61825 Thu, 09 Dec 2021 17:13:00 -0000 https://status.bl.ink/incident/61825#3581ccbc4b507fcb640ba11e8edcf6b40d4e081b5984a9621ae38ad96c5899df An application error has been returned across some services across some customer sites. We are investigating. Sites are currently online again, but we are researching the root cause. https://status.bl.ink/incident/61596 Wed, 08 Dec 2021 00:13:14 -0000 https://status.bl.ink/incident/61596#1f9b913935729d4a20116fe48f76ff3862ab6a6719b2206f1a4d03451aecf16f Services have been fully restored and all systems should be operating normally. We will continue to monitor to ensure everything is working as expected. Should you have any ongoing issues, please reach out to us. Thank you for your patience and support during the outage. We are grateful for your partnership. https://status.bl.ink/incident/61596 Tue, 07 Dec 2021 23:13:42 -0000 https://status.bl.ink/incident/61596#21fd653fa525ea3baff98d649642a791a69172181be17b226fbf4c8ec7b257f7 We are still waiting on full service restoration from AWS, however we have been successful in re-routing services through a secondary cluster. Access to management consoles and link redirect are now operational, however SSL services are still impacted. It is likely that you will see SSL warnings until these certificates can be transitioned, however non-SSL routing is operational. https://status.bl.ink/incident/61596 Tue, 07 Dec 2021 21:38:31 -0000 https://status.bl.ink/incident/61596#f958b00fe9803209cbbdd41b5c5b26c3dcbaec582ceabd117789bacf0c9e98c0 We are still waiting on a status update from AWS on service restoration. Our teams are actively working on alternative recovery options to bring critical services back online as soon as possible Thank you for your patience and understanding. https://status.bl.ink/incident/61596 Tue, 07 Dec 2021 19:53:30 -0000 https://status.bl.ink/incident/61596#80d728b2898a26f6320bb212f5e7ca7c49386ad5d90df21b3af95db84fd84f62 We are still awaiting an update from AWS regarding restoration of services. AWS shared "The root cause of this issue is an impairment of several network devices in the US-EAST-1 Region. We are pursuing multiple mitigation paths in parallel, and have seen some signs of recovery, but we do not have an ETA for full recovery at this time." We will provide another update as soon as more information is available. We are actively reviewing restoration options to expedite our full return to service. https://status.bl.ink/incident/61596 Tue, 07 Dec 2021 19:03:43 -0000 https://status.bl.ink/incident/61596#36abd6041ed407083d9c543e7bd9b5ffd3430f4426a89a0f5f94d25c53e3f681 The root cause of the service outage has been linked to the AWS outage reported in the US-East region, where many of our services are hosted. AWS reports that they are starting to see signs of recovery, but no ETA for a full recovery has been provided at this time. We are evaluating restoration options to expedite our recovery time. The AWS status page is located here: https://status.aws.amazon.com https://status.bl.ink/incident/61596 Tue, 07 Dec 2021 18:39:21 -0000 https://status.bl.ink/incident/61596#7e36bc385e7ceafa09434e5d4f740cb2cdafae8498a7c52fb14d986c9153e54e An outage is causing downtime across multiple services. We are currently investigating and will post updates here as they are available. https://status.bl.ink/incident/58347 Sat, 13 Nov 2021 18:13:41 -0000 https://status.bl.ink/incident/58347#418abb8abfc2475ecc07e34b4ac3cd53fba955a9a473a014563e6120d5402fbb Our primary database cluster will be offline for up to 5 minutes at approximately 12:00pm Central time (17:00 UTC) for a critical maintenance update in order to implement a multi-cluster configuration. This will impact all customers during the brief window where we restart our database services. The net impact should be minimal, but any traffic to links, API, or console will be delayed or unresponsive. For any questions regarding this maintenance window, please contact us using the "Get in touch" button above. https://status.bl.ink/incident/58347 Sat, 13 Nov 2021 18:13:41 -0000 https://status.bl.ink/incident/58347#418abb8abfc2475ecc07e34b4ac3cd53fba955a9a473a014563e6120d5402fbb Our primary database cluster will be offline for up to 5 minutes at approximately 12:00pm Central time (17:00 UTC) for a critical maintenance update in order to implement a multi-cluster configuration. This will impact all customers during the brief window where we restart our database services. The net impact should be minimal, but any traffic to links, API, or console will be delayed or unresponsive. For any questions regarding this maintenance window, please contact us using the "Get in touch" button above. https://status.bl.ink/incident/58347 Sat, 13 Nov 2021 18:05:00 +0000 https://status.bl.ink/incident/58347#4bfa86dee508db8c884b8a1e65aacde07f9ca52b308127d5577a8ea7be7f3016 Maintenance completed https://status.bl.ink/incident/58347 Sat, 13 Nov 2021 18:05:00 +0000 https://status.bl.ink/incident/58347#4bfa86dee508db8c884b8a1e65aacde07f9ca52b308127d5577a8ea7be7f3016 Maintenance completed https://status.bl.ink/incident/58347 Sat, 13 Nov 2021 18:00:00 -0000 https://status.bl.ink/incident/58347#418abb8abfc2475ecc07e34b4ac3cd53fba955a9a473a014563e6120d5402fbb Our primary database cluster will be offline for up to 5 minutes at approximately 12:00pm Central time (17:00 UTC) for a critical maintenance update in order to implement a multi-cluster configuration. This will impact all customers during the brief window where we restart our database services. The net impact should be minimal, but any traffic to links, API, or console will be delayed or unresponsive. For any questions regarding this maintenance window, please contact us using the "Get in touch" button above. https://status.bl.ink/incident/58347 Sat, 13 Nov 2021 18:00:00 -0000 https://status.bl.ink/incident/58347#418abb8abfc2475ecc07e34b4ac3cd53fba955a9a473a014563e6120d5402fbb Our primary database cluster will be offline for up to 5 minutes at approximately 12:00pm Central time (17:00 UTC) for a critical maintenance update in order to implement a multi-cluster configuration. This will impact all customers during the brief window where we restart our database services. The net impact should be minimal, but any traffic to links, API, or console will be delayed or unresponsive. For any questions regarding this maintenance window, please contact us using the "Get in touch" button above. https://status.bl.ink/incident/58347 Sat, 06 Nov 2021 17:31:09 -0000 https://status.bl.ink/incident/58347#418abb8abfc2475ecc07e34b4ac3cd53fba955a9a473a014563e6120d5402fbb Our primary database cluster will be offline for up to 5 minutes at approximately 12:00pm Central time (17:00 UTC) for a critical maintenance update in order to implement a multi-cluster configuration. This will impact all customers during the brief window where we restart our database services. The net impact should be minimal, but any traffic to links, API, or console will be delayed or unresponsive. For any questions regarding this maintenance window, please contact us using the "Get in touch" button above. https://status.bl.ink/incident/58347 Sat, 06 Nov 2021 17:31:09 -0000 https://status.bl.ink/incident/58347#418abb8abfc2475ecc07e34b4ac3cd53fba955a9a473a014563e6120d5402fbb Our primary database cluster will be offline for up to 5 minutes at approximately 12:00pm Central time (17:00 UTC) for a critical maintenance update in order to implement a multi-cluster configuration. This will impact all customers during the brief window where we restart our database services. The net impact should be minimal, but any traffic to links, API, or console will be delayed or unresponsive. For any questions regarding this maintenance window, please contact us using the "Get in touch" button above.