BrightSign Outage History

BrightSign is up right now

Pingoru has recorded 8 incidents for BrightSign: 7 in the last 12 months and 1 in the last 90 days.

Source: status.bsn.cloud

8incidents recorded
7last 12 months
1last 90 days
12 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOctNov1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov1%
Pingoru began tracking BrightSign in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 2026278 of 744 (10%)
June 202622 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202612 of 162 (1%)

Incidents, newest first

Minor November 6, 2026 BSN.Cloud API degraded performance 1h 53m BSN.Cloud Platform (BSN.Cloud Provisioning), BSN.Cloud Platform (BSN.Cloud API), BSN.Cloud Platform (BSN.Cloud Admin Panel), BSN.Cloud Platform (BSN.Cloud Control Panel) and 3 more

Started Nov 06, 2026, 07:30 PM UTC· resolved Nov 06, 2026, 09:23 PM UTC

  1. investigating Nov 06, 2026, 07:30 PM UTC

    BSN.Cloud is experiencing extremely high database load and is causing the API to be degraded. We are currently investigating the cause.

  2. resolved Nov 06, 2026, 09:23 PM UTC

    The issue was resolved with a patch to remove the problematic code. Impact: Every service using this database was slowed down, including BrightSign Control and device check-ins. All players that were trying to provision did not get a response.

Read the full incident report →

Major June 11, 2026 brightsignnetwork.com (BSN.com) issues logging in 15m BSN.com Platform (BSN.com Platform)

Started Jun 11, 2026, 06:54 PM UTC· resolved Jun 11, 2026, 07:10 PM UTC

  1. investigating Jun 11, 2026, 04:30 PM UTC

    We have been made aware that some customers are having issues logging into BrightSignNetwork.com. We are currently investigating the problem.

  2. monitoring Jun 11, 2026, 06:55 PM UTC

    We have looking into the issues logging in to brightsignnetwork.com. We have done some maintenance on our servers and rebooted, and things appear to be improving. We will continue to monitor the situation.

  3. resolved Jun 11, 2026, 07:10 PM UTC

    Customers are reporting they are now logging to brightsignnetwork.com successfully.

Read the full incident report →

Major June 1, 2026 File uploads to BSN.Cloud are currently unavailable 1h 32m BSN.Cloud Platform (BSN.Cloud API), BSN.Cloud Platform (BA Connected Application)

Started Jun 01, 2026, 11:02 AM UTC· resolved Jun 01, 2026, 12:35 PM UTC

  1. identified Jun 01, 2026, 11:02 AM UTC

    File uploads to BSN.Cloud are currently unavailable following today's platform updates. Engineering is actively investigating and working toward resolution.

  2. resolved Jun 01, 2026, 12:35 PM UTC

    Our engineers have now resolved the issue and file uploading is now working.

Read the full incident report →

Major May 26, 2026 BSN.cloud New User Registration is unavailable 1h 9m BSN.Cloud Platform (BSN.Cloud Authentication Server)

Started May 26, 2026, 06:50 AM UTC· resolved May 26, 2026, 07:59 AM UTC

  1. investigating May 26, 2026, 06:50 AM UTC

    BSN.cloud new user registration is currently unavailable. We are currently investigating the problem.

  2. identified May 26, 2026, 07:48 AM UTC

    We have identified the new user registration issue and we are now rolling out a fix to address the problem.

  3. resolved May 26, 2026, 07:59 AM UTC

    We've identified and fixed the cause of new user registration failures on BSN.cloud. The issue was due to a problem with an authentication server component related to the user registration flow.

Read the full incident report →

Minor May 8, 2026 AWS Thermal Event causing operational issues 3d 4h BSN.Cloud Platform (BSN.Cloud Provisioning), BSN.Cloud Platform (BSN.Cloud API), BSN.Cloud Platform (BSN.Cloud Admin Panel), BSN.Cloud Platform (BSN.Cloud Control Panel) and 4 more

Started May 08, 2026, 01:52 AM UTC· resolved May 11, 2026, 06:52 AM UTC

  1. investigating May 08, 2026, 01:52 AM UTC

    We’re currently investigating an AWS thermal event affecting our infrastructure in USE-1. This is causing periodic pod restarts across our platform as AWS performs thermal management on the affected hardware. Our Kubernetes cluster is actively managing these restarts, and BSN.cloud services remain operational. You may experience brief latency spikes or momentary connection resets as affected pods cycle, but core functionality is maintained. What we’re doing: • Actively monitoring pod restart patterns and cluster health • Working with AWS on the underlying thermal issue • Standing by to escalate or migrate workloads if operational impact increases

  2. monitoring May 08, 2026, 05:19 AM UTC

    We continue to monitor our systems closely following the AWS thermal event. The situation appears to be stabilizing: Pod restart frequency has decreased, and our systems are recovering as expected. BSN.cloud services remain fully operational with no impact to your workflows. AWS Update: AWS has reported that the underlying thermal issue is beginning to resolve. We’re tracking their progress and will continue monitoring our infrastructure for any further activity. We’ll maintain close observation over the next few hours and will provide another update if the situation changes. Thank you for your patience

  3. resolved May 09, 2026, 11:00 AM UTC

    All systems are operating as normal.

Read the full incident report →

Notice December 5, 2025 Cloudflare API is offline 17m

Started Dec 05, 2025, 09:12 AM UTC· resolved Dec 05, 2025, 09:30 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major November 10, 2025 BSN.Cloud operational issues 1h 55m

Started Nov 10, 2025, 12:09 PM UTC· resolved Nov 10, 2025, 02:04 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor October 20, 2025 AWS Infrastructure Outage 1h 36m

Started Oct 20, 2025, 08:19 AM UTC· resolved Oct 20, 2025, 09:56 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →