Vitally Outage History
Vitally is up right nowPingoru has recorded 50 incidents for Vitally: 14 in the last 12 months and 0 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 | 3 | 2 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 | 0 | 0 of 585 (0%) |
Incidents, newest first
Minor February 17, 2025 Degraded performance in US 2d 11h Product
Started Feb 17, 2025, 06:19 AM UTC· resolved Feb 19, 2025, 06:00 PM UTC
- investigating Feb 17, 2025, 06:19 AM UTC
Vitally is experiencing an unusual amount of server timeouts. We are looking into the incident.
- identified Feb 17, 2025, 06:43 AM UTC
We have mitigated the issue, though background jobs may experience delays.
- resolved Feb 19, 2025, 06:00 PM UTC
Due to the database maintenance we performed on Feb 15, our database was struggling to handle operational load. We rolled back some of those changes and have prioritized work to optimize our database usage to prevent incidents like this in the future.
Major February 13, 2025 Elevated Error Rates in EU 4h 30m Product, Analytics Data Processing
Started Feb 13, 2025, 11:20 PM UTC· resolved Feb 14, 2025, 03:51 AM UTC
- investigating Feb 13, 2025, 11:20 PM UTC
We are seeing elevated error rates in requests and general operations in our EU data center. This appears to be an issue internal to AWS but we are monitoring
- identified Feb 13, 2025, 11:40 PM UTC
AWS has acknowledged their outage https://health.aws.amazon.com/health/status Operational issue - Multiple services (Stockholm) Service Multiple services Severity Impacted RSS Increased Error Rates and Latencies Feb 13 3:35 PM PST We are investigating increased error rates and latencies for AWS Services in the EU-NORTH-1 Region.
- identified Feb 13, 2025, 11:58 PM UTC
AWS has provided an update ~2 minutes ago. We can confirm that the networking issues within the eu-north-1 region persist and affect connectivity to the Vitally web app as well as Vitally's ability to receive analytics data via our APIs Feb 13 3:55 PM PST We can confirm increased error rates and latencies for multiple AWS Services in the EU-NORTH-1 Region. This is due to a networking issue that we are actively working to mitigate as quickly as possible, and have all engineers engaged at this time. This issue is not impacting connectivity to and from the region, but is impacting inter-region traffic. During this time, the bulk of the impact will be contained to eun1-az3, but some individual services and operations may be impacted in other zones in the EU-NORTH-1 Region. If possible, we recommend weighting traffic away from AZ eun1-az3. We will provide an additional update within the next 45 minutes, or sooner if we have additional information to share.
- identified Feb 14, 2025, 12:32 AM UTC
AWS has just provided an update, though we are still seeing an elevated error rate. Thank you for your patience as our infrastructure provider addresses their issue Feb 13 4:31 PM PST We are seeing early signs of recovery for error rates and latencies for multiple AWS Services in the EU-NORTH-1 Region. As we work toward full recovery, some requests may continue to timeout or be throttled. We recommend customers retry failed requests where possible. We will continue to provide additional information as we have it, or within the next 60 minutes.
- resolved Feb 14, 2025, 03:51 AM UTC
We have seen error rates return to our baseline levels. AWS's most recent update indicates successful mitigation. We will continue to monitor but are not expecting impact to business hours operations in our EU data center.
Major January 27, 2025 Dashboards are currently broken 17m Product
Started Jan 27, 2025, 03:27 PM UTC· resolved Jan 27, 2025, 03:44 PM UTC
- identified Jan 27, 2025, 03:27 PM UTC
We are investigating an issue where dashboards are erroring. We have identified the issue and service should be restored shortly.
- identified Jan 27, 2025, 03:33 PM UTC
A fix is being deployed and is expected to be live in 10-15 minutes.
- resolved Jan 27, 2025, 03:44 PM UTC
This incident has been resolved, but we will continue to monitor closely.
Minor January 3, 2025 Playbook Execution Delays 3d 5h Product
Started Jan 03, 2025, 03:12 PM UTC· resolved Jan 06, 2025, 08:16 PM UTC
- investigating Jan 03, 2025, 03:12 PM UTC
Our playbook execution infrastructure is experiencing an unusually high number of jobs in our EU data centers, causing playbook executions to be delayed up to several hours. The delays started approximately 8 hours ago. No data has been lost, and playbook execution is almost caught up.
- monitoring Jan 03, 2025, 11:01 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 06, 2025, 08:16 PM UTC
This incident has been resolved.
Notice November 25, 2024 Login page loading errors 20m
Started Nov 25, 2024, 05:30 PM UTC· resolved Nov 25, 2024, 05:50 PM UTC
- resolved Nov 25, 2024, 06:07 PM UTC
Starting at 12:50 PM EST, we experienced errors when loading the login page. This has now been resolved.
Major November 18, 2024 External doc sharing errors 45m Product
Started Nov 18, 2024, 08:38 PM UTC· resolved Nov 18, 2024, 09:23 PM UTC
- investigating Nov 18, 2024, 08:38 PM UTC
We are currently investigating an issue with external docs shared on Vitally not loading correctly. The core product remains available.
- identified Nov 18, 2024, 08:43 PM UTC
The issue has been identified and a fix is rolling out now.
- identified Nov 18, 2024, 09:20 PM UTC
We are continuing to work on a fix for this issue.
- resolved Nov 18, 2024, 09:23 PM UTC
This incident has been resolved.
Minor October 30, 2024 Elevated Analytics API Errors 23m
Started Oct 30, 2024, 04:30 PM UTC· resolved Oct 30, 2024, 04:53 PM UTC
- resolved Oct 30, 2024, 05:00 PM UTC
We experienced an elevated level of Analytics API errors in our EU region for less than 10 minutes, from 16:45 UTC - 16:53 UTC. Some requests to the Analytics API failed with a 504 error during this time. The error rate has since recovered. We have identified the issue and are working to mitigate it moving forward.