ChatGPT Status · History · Incident #4751
RESOLVEDChatGPT failing to load or save
Minor · Started Jun 18, 2026 · 3:26 AM
⚡ Pulsetic detected this 600 minutes before ChatGPT acknowledged it
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
ChatGPT Status · History · Incident #4751
RESOLVEDMinor · Started Jun 18, 2026 · 3:26 AM
⚡ Pulsetic detected this 600 minutes before ChatGPT acknowledged it
Duration
28m
Severity
Minor
Detection lead
600 min
User reports
Peak 1/hr
Summary
All impacted services have now fully recovered.
Started
Jun 18, 2026 · 3:26 AM
Resolved
Jun 18, 2026 · 3:55 AM
Duration
28m
Severity
Minor
Detection lead
Pulsetic detected
~600 min before acknowledgement
User reports and synthetic probes crossed the detection threshold
ChatGPT acknowledged
Jun 18, 2026 · 3:26 AM
Event timeline
Detected by Pulsetic
Jun 17 · 5:26 PM PulseticUser reports and synthetic probes crossed the detection threshold — 600 min before the official acknowledgement.
Investigating
Jun 18 · 3:26 AM ChatGPTWe are investigating the issue for the listed services.
Monitoring
Jun 18 · 3:43 AM ChatGPTWe have applied the mitigation and are monitoring the recovery.
Resolved
Jun 18 · 3:55 AM ChatGPTAll impacted services have now fully recovered.
User reports · incident window
Hourly report count. Red bars mark the incident window.
Peak: 1 reports/hr
Pulsetic catches degradations minutes before vendors acknowledge them. This one: 600 minutes early.
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