About our Blackboard Core Data status page integration

• Early Warning Signals

  If we detect a potential Blackboard Core Data outage or other issue before it was reported on the official status page we will send an Early Warning Signal notification to StatusGator subscribers. We can often detect issues before they are officially acknowledged by the provider, giving you a head start on resolving any potential problems.

• Down notifications

  If Blackboard Core Data is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

• Warning notifications

  Warn notifications are used when Blackboard Core Data is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

• Maintenance notifications

  Blackboard Core Data posts separate notifications for planned maintenance work. StatusGator will notify subscribers when Blackboard Core Data enters a pre-planned maintenance window, keeping you up to date.

• Status messages

  When Blackboard Core Data posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

• Status details

  When Blackboard Core Data has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

• Component status filtering

  Because Blackboard Core Data has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you whenever a particular component is down. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.