Follow the recent outages and downtime for GrapheneDB in the table below.
Start Time |
Type |
Length |
Message |
Details |
|||||
---|---|---|---|---|---|---|---|---|---|
July 10, 2022 17:56 UTC |
WARN |
about 5 hours |
AWS is reporting issues in the eu-west-2 region |
See more
|
|||||
February 24, 2022 17:01 UTC |
DOWN |
25 minutes |
GrapheneDB documentation page issue |
See more
|
|||||
January 05, 2022 13:41 UTC |
WARN |
15 minutes |
GrapheneDB admin interface is down |
See more
|
|||||
January 05, 2022 13:16 UTC |
DOWN |
25 minutes |
GrapheneDB admin interface is down |
See more
|
|||||
January 05, 2022 13:02 UTC |
DOWN |
4 minutes |
GrapheneDB admin interface is down |
See more
|
|||||
2024-04-11 14:36:10 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-04-11 14:36:10 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-04-11 14:36:10 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-04-11 14:36:10 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2024-04-11 14:36:10 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more |
Sign Up for More GrapheneDB History
StatusGator has over 7 years of GrapheneDB status history.
View details of the current GrapheneDB status below.
Name |
Status |
Details |
---|---|---|
GrapheneDB All Operations |
UP | See more |
GrapheneDB Cluster Tier |
UP | See more |
GrapheneDB Documentation page |
UP | See more |
GrapheneDB Management API |
UP | See more |
GrapheneDB New deployment only |
UP | See more |
GrapheneDB Single Tier |
UP | See more |
GrapheneDB User Interface |
UP | See more |
GrapheneDB Website |
UP | See more |
GrapheneDB status, last 24 hours:
Up: 24 hours
Warn: 0 minutes
Down: 0 minutes
Maintenance: 0 minutes
We've been monitoring GrapheneDB outages since January 6, 2017.
Here's the history of service outages we've observed from the GrapheneDB Status Page:
GrapheneDB is a Database solution that StatusGator has been monitoring since January 2017. Over the past over 7 years, we have collected data on on more than 83 outages that affected GrapheneDB users. When GrapheneDB publishes downtime on their status page, they do so across 8 components using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.
Many StatusGator users monitor GrapheneDB to get notified when it's down, is under maintenance, or has an outage. We've sent more than 200 notifications to our users about GrapheneDB incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.
If GrapheneDB 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.
Warn notifications are used when GrapheneDB 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.
GrapheneDB posts separate notifications for planned maintenance work. StatusGator will notify subscribers when GrapheneDB enters a pre-planned maintenance window, keeping you up to date.
Since GrapheneDB publishes a feed of proactive maintenance events on their status page, StatusGator will collect information about these events. Maintenance events for all your services can be viewed within StatusGator as a unified feed.
When GrapheneDB posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.
When GrapheneDB 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.
Because GrapheneDB has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. 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.
Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!
Are you experiencing issues with GrapheneDB? Sign up to receive notifications when GrapheneDB publishes outages.
GrapheneDB Down or not working? Never be taken by surprise again.
StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,580 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.
Looking for recent downtime and outages of GrapheneDB?
Sign up for StatusGator and see all historical information about GrapheneDB outages and performance issues. Get free, instant notifications when GrapheneDB goes down.