GoBright Outage History
GoBright is up right nowPingoru has recorded 43 incidents for GoBright: 4 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 1 | 7 of 573 (1%) |
Incidents, newest first
Notice October 21, 2026 Service update 6h 59m Displays (T1B - Meet-Work-Visit (Europe)), Displays (T2B - Meet-Work-Visit (Europe)), Displays (T3B - Meet-Work-Visit (Oceania)), Displays (UK1B - Meet-Work-Visit (United Kingdom)) and 2 more
Started Oct 21, 2026, 11:08 AM UTC· resolved Oct 21, 2026, 06:07 PM UTC
- monitoring Oct 21, 2026, 11:08 AM UTC
`install.gobright.cloud` has been temporarily taken offline due to recently discovered PHP vulnerabilities. The impact of this is that app updates on devices/displays cannot be executed. Our platform remains fully operational and is not affected, as it does not use PHP. You can continue using the platform by logging in at: [https://portal.gobright.cloud](https://portal.gobright.cloud/)
- resolved Oct 21, 2026, 06:07 PM UTC
This incident has been resolved.
Minor January 26, 2026 Interact devices commissioned to UK hosting having connection issues 2h 29m
Started Jan 26, 2026, 09:38 AM UTC· resolved Jan 26, 2026, 12:07 PM UTC
- investigating Jan 26, 2026, 09:38 AM UTC
We are currently investigating this incident..
- identified Jan 26, 2026, 09:56 AM UTC
Currently there are problems with the Azure IoTHub in the UK South datacenter. Microsoft is working on this issue (Azure issue reference: VK8M-LXZ), and we are closely monitoring the progress of the fix, and if we can expedite the fix. .
- monitoring Jan 26, 2026, 11:19 AM UTC
The Azure IoTHub in the UK South datacenter is recovering, and services are now getting back to normal operation..
- resolved Jan 26, 2026, 12:07 PM UTC
This incident has been resolved..
Minor December 20, 2025 Commissioning of IPv6 Inbound IP Addresses – Overall
Started Dec 20, 2025, 07:00 AM UTC· resolved Dec 20, 2025, 07:00 AM UTC
No vendor updates were posted for this incident.
Major September 25, 2025 Platform unavailable 18m
Started Sep 25, 2025, 10:28 AM UTC· resolved Sep 25, 2025, 10:46 AM UTC
- investigating Sep 25, 2025, 10:28 AM UTC
We are currently investigating this incident..
- identified Sep 25, 2025, 10:33 AM UTC
We are continuing to work on a fix for this incident..
- monitoring Sep 25, 2025, 10:37 AM UTC
We implemented a fix and are currently monitoring the result..
- resolved Sep 25, 2025, 10:46 AM UTC
This incident has been resolved..
Minor May 23, 2025 Commissioning of new outbound IP addresses –
Started May 23, 2025, 11:00 PM UTC· resolved May 23, 2025, 11:00 PM UTC
No vendor updates were posted for this incident.
Minor March 20, 2025 Occassional performance degration (t1b hosting) 42m
Started Mar 20, 2025, 07:45 AM UTC· resolved Mar 20, 2025, 08:27 AM UTC
- investigating Mar 20, 2025, 07:45 AM UTC
T1B hosted customers can experience occasional performance degration, we are currently investigating this incident..
- monitoring Mar 20, 2025, 08:05 AM UTC
We implemented a fix and are currently monitoring the result..
- resolved Mar 20, 2025, 08:27 AM UTC
This incident has been resolved..
Major February 3, 2025 Desk/Parking booking in half/fullday mode showing 'unavailable' (t1b & t3b hosting) 2h 5m
Started Feb 03, 2025, 09:00 AM UTC· resolved Feb 03, 2025, 11:05 AM UTC
- investigating Feb 03, 2025, 09:00 AM UTC
Desk/parking bookings in halfday or fullday mode can show 'unavailable' in some situations. The issue is only occurring on the t1b & t3b hosting environments. We are working on a fix as soon as possible, expected in the next hours. Workaround: Click on 'advanced booking' in the popup, then it is possible to proceed with the booking..
- identified Feb 03, 2025, 09:02 AM UTC
We have identified the cause of the problem and are taking the necessary steps to resolve the issue..
- monitoring Feb 03, 2025, 10:48 AM UTC
We deployed a fix and are currently monitoring the result..
- resolved Feb 03, 2025, 11:05 AM UTC
This incident has been resolved..