OVHcloud is
experiencing issues.
Pulsetic can detect an outage before the provider officially reports it. 122 incidents on record since Mar 2026
Last updated: 5 min ago · 0 user reports (24h)
Pulsetic can detect an outage before the provider officially reports it. 122 incidents on record since Mar 2026
Last updated: 5 min ago · 0 user reports (24h)
Started 2 hours ago · Oct 8, 2026 · 3:14 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Object Storage S3 offer on the specific EU-WEST-PAR region. Here are some supplementary details : <b>Start time :</b> 08/10/2026 00:00 UTC <b>Impacted Service(s) :</b> Latency observed for Object Storage S3 in the specified region. <b>Customers Impact :</b> Customers may still experience some latency when accessing and using their objects located in EU-WEST-PAR region, though it has significantly decreased. <b>Root Cause :</b> This incident is caused by a software issue. <b>Ongoing Actions :</b> The incident has been identified and a significant reduction in latency has been observed. Our teams remain mobilised to fully restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Bars represent 20-min intervals. Occasional spikes may reflect individual issues, not widespread outages.
Latest 50 reports from the last 48 hours
Pulsetic is website uptime monitoring. Add a website you own and it gets checked as often as every 30 seconds on the Team plan, so the next answer arrives by email.
10 monitors free, checked every 5 minutes, with email alerts on failure and recovery. No credit card.
Click an issue to upvote it and help us better indicate the service status.
Have a different problem?
Distribution of reported issues over the last 24 hours.
Total Incidents
68
Jul 10 to Oct 8, 2026
Major / Critical
39
57% of the total
Minor Incidents
29
Avg. 0.3 per day
Median Resolution
1h 32m
P95: 42h 45m
Across all 4,379 services Pulsetic tracks, the incidents their status pages reported over the last 12 months had a median resolution time of 2h 4m, and 35% were rated major or critical by the provider. These numbers are calculated separately from the 90-day figures for OVHcloud above.
Source: The State of Uptime 2026, figures as of .
From official status page
| Incident | Started | Duration | Impact | Status | Link |
|---|---|---|---|---|---|
[EU-WEST-PAR][Storage] - Object Storage S3 incident notification |
Oct 8, 2026 · 3:14 PM | Ongoing | Minor |
Identified |
Details → |
[EU/CA][Storage] - Cold Archive Incident notification |
Oct 8, 2026 · 7:41 AM | < 1m | None |
Resolved |
Details → |
[EU-WEST-PAR][Storage] - Object Storage S3 incident notification |
Oct 7, 2026 · 4:39 PM | < 1m | None |
Resolved |
Details → |
[EU/CA][Containers & Orchestration] - Managed Kubernetes Service/ Managed Private Registry incident notification |
Oct 7, 2026 · 1:25 PM | 37m | Major |
Resolved |
Details → |
[EU/CA][Storage] - Object Storage S3 incident notification |
Oct 7, 2026 · 1:11 PM | 50m | Major |
Resolved |
Details → |
[AF-NORTH/EU-WEST/EU-NORTH][LocalZones] - IPv6 incident notification |
Oct 7, 2026 · 12:27 PM | < 1m | None |
Resolved |
Details → |
[GRA][Compute - Instance] - Some Instances incident notification |
Oct 7, 2026 · 5:42 AM | < 1m | None |
Resolved |
Details → |
[GRA5/GRA7][Compute - Instance] - Some Instances incident notification |
Oct 4, 2026 · 1:47 PM | < 1m | None |
Resolved |
Details → |
[GRA][Storage] - Object Storage S3 incident notification |
Oct 3, 2026 · 3:06 AM | 2d 8h 40m | Major |
Resolved |
Details → |
[US-EAST-LZ-MIA][Network] - Localzone incident notification |
Oct 1, 2026 · 6:09 AM | 1h 54m | Major |
Resolved |
Details → |
How do they compare?
DigitalOcean
Cloud hosting
Linode
Cloud hosting
UpCloud
Cloud hosting
More in Cloud hosting
Common questions
Check the status badge at the top of this page for the current status. Pulsetic follows the official status page and cross-references it with user reports to give you the most accurate picture.
Based on our 90-day data, we've recorded 68 incidents, of which 39 were major or critical. The median resolution time is 1h 32m.
Pulsetic follows the official status page and records the incidents the provider posts there. Crowdsourced user reports and Pulsetic's own synthetic checks add an early warning, which can surface an issue before the official status page mentions it.
The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.
"Never acknowledged" means Pulsetic recorded a service disruption from user reports and its own checks, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.
Add it as a dependency monitor. The Free plan includes one. See how it works
No credit card needed
Help us pinpoint the issue
Tell us what you're seeing, and we'll correlate your report with others from around the world.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.