Snapshot 24581
Normalized text
Scripts and page chrome removed; this is what change detection compares.
All systems operational System status Jul 2026 - Sep 2026 No components configured Platform - app.phare.io - 65ms Availability 99.9885% No data Operational 90 days ago 99.9885% availability Today Website - phare.io - 60ms Availability 100% No data Operational 90 days ago 100% availability Today API - api.phare.io - 112ms Availability 99.6745% No data Operational 90 days ago 99.6745% availability Today Documentation - docs.phare.io - 142ms Availability 100% No data Operational 90 days ago 100% availability Today Blog - phare.io/blog - 62ms Availability 100% No data Operational 90 days ago 100% availability Today Incidents Jul 2026 - Sep 2026 No incident was recorded for this time period. Partial outage Monitoring down in the United-Kingdom region Affected components: Platform - app.phare.io Timeline: Sep 24, 2026, 1:30 PM UTC – Sep 24, 2026, 1:44 PM UTC · Lasted 14 minutes 52 seconds Incident updates: resolved Sep 24, 2026, 1:43 PM UTC The uptime monitoring agent is now up and running. investigating Sep 24, 2026, 1:37 PM UTC The uptime monitoring agent running in the UK has been reporting connectivity issues for a few minutes before going down. We're investigating the situation to bring it up. Partial outage Firewall blocking in the Germany region Affected components: Platform - app.phare.io Timeline: Sep 8, 2026, 6:00 AM UTC – Sep 8, 2026, 8:30 AM UTC · Lasted 2 hours 30 minutes Incident updates: resolved Sep 8, 2026, 8:30 AM UTC Rotating the IP solved the issue, we will continue to monitor the situation with Bunny.net to avoid any new occurrence of a shared IP flagging affecting the Phare uptime monitoring agent. monitoring Sep 8, 2026, 7:30 AM UTC The uptime monitoring agent has been rotated to another IP to temporarily fix the issue, Bunny.net support has been contacted to provide a long term fix. identified Sep 8, 2026, 6:00 AM UTC Phare uses a set of shared IP for the uptime monitoring agent running in Germany. One of the IP (79.127.216.*) has been added to abuseipdb.com. This list is used by hosting provider and firewalls to automatically block abusive traffic. This block prevents Phare from accessing your monitor, usually yielding a "TLS handshake timed out" error. Partial outage DNS failover failure in the France region Affected components: Platform - app.phare.io Timeline: Aug 13, 2026, 5:24 AM UTC – Aug 13, 2026, 8:21 AM UTC · Lasted 2 hours 57 minutes Incident updates: resolved Aug 13, 2026, 8:24 AM UTC The issue has been fixed, a more thorough investigation will be done to avoid future failover issue. identified Aug 13, 2026, 5:25 AM UTC All Phare monitoring agents experienced timeouts with Cloudflare DNS, the failover in place was able to switch to another provider except in the France region that stayed stuck in a failed state, reporting "DNS server did not respond properly" incidents for all monitors. Degraded performance Inaccurate timeout reporting Affected components: Platform - app.phare.io Timeline: May 27, 2026, 9:46 PM UTC – Jul 15, 2026, 3:28 PM UTC · Lasted 48 days 17 hours 42 minutes Incident updates: resolved Jul 15, 2026, 1:26 PM UTC Phare's infrastructure provider deployed multiple connectivity improvements over the past weeks. The issue should now be fully solved for all monitors. monitoring Jun 6, 2026, 7:13 PM UTC A single ASN is still experiencing false-positive timeouts, affecting 0.2% of websites monitored on Phare. monitoring May 31, 2026, 8:13 AM UTC Remaining monitors experiencing false-positive timeouts are tied to a subset of ASN, we are working with the hosting provider of Phare's uptime monitoring agent to solve the issue. monitoring May 29, 2026, 12:09 PM UTC A new version of the uptime monitoring agent has been deployed around 01:00:00 UTC today, the number of reported timeouts has since then reduced, but the issue still affects a small subset of monitors. monitoring May 28, 2026, 12:14 PM UTC A new version of the uptime monitoring agent is currently being tested in a pre-production environment. This step will take several hours to ensure the patch fix the inaccurate timeout reporting and does not introduce other issues. identified May 28, 2026, 9:49 AM UTC Phare may inaccurately report timeouts issues on monitors, the issue is identified on a specific path of the core TLS certificate validation process (OCSP & AIA) and a patch is being worked on. Maintenance Jul 2026 - Sep 2026 No maintenance was recorded for this time period.