Automated systems detected a related issue (Upstream ID: q2bck6r39bzk). We will continuously monitor and evaluate the impact on our services. We will provide updates if there is further progress.
Resolved: The upstream provider has successfully resolved the issue.
INVESTIGATINGID: 787f465a97c1
Automated systems detected a related issue (Upstream ID: 2dpbcq5j165n). We will continuously monitor and evaluate the impact on our services. We will provide updates if there is further progress.
Resolved: The upstream provider has successfully resolved the issue.
INVESTIGATINGID: 8f11f0cea3a2
Automated systems detected a related issue (Upstream ID: 4m03612lprhr). We will continuously monitor and evaluate the impact on our services. We will provide updates if there is further progress.
Resolved: The upstream provider has successfully resolved the issue.
INVESTIGATINGID: 2b56d00461fc
Automated systems detected a related issue (Upstream ID: dwfzz0bwhmsq). We will continuously monitor and evaluate the impact on our services. We will provide updates if there is further progress.
Resolved: The upstream provider has successfully resolved the issue.
INVESTIGATINGID: 9558ae1608f9
Automated systems detected a related issue (Upstream ID: dcmwvjwfyhjg). We will continuously monitor and evaluate the impact on our services. We will provide updates if there is further progress.
[MINOR]Automated Alert: DeepL API Reachability
-
#
RESOLVED
RESOLVEDID: 59f4e075e4e3
Resolved: The upstream provider has successfully resolved the issue.
INVESTIGATINGID: e88b64ddcc7d
Automated systems detected a related issue (Upstream ID: inc_deepl_api_disruption). We will continuously monitor and evaluate the impact on our services. We will provide updates if there is further progress.
Resolved: The upstream provider has successfully resolved the issue.
INVESTIGATINGID: 97521f928f65
Automated systems detected a related issue (Upstream ID: n3n98pb4x9f4). We will continuously monitor and evaluate the impact on our services. We will provide updates if there is further progress.
At 10:01 UTC on September 13, we noticed stability issues across several GitHub services, including their API, Requests, Issues, Pages, and Pull Requests. Since our service relies on GitHub Pages, we monitored the situation closely and confirmed the resolution at 11:01 UTC. After a follow-up review, we've determined that this incident did not actually impact our services.
RESOLVEDID: 62a646e8af66
Resolved: The upstream provider has successfully resolved the issue.
INVESTIGATINGID: c7a6baccbabf
Automated systems detected a related issue. We will continuously monitor and evaluate the impact on our services. We will provide updates if there is further progress.
On September 11, 2026, at 20:01 UTC, our system received a report from Cloudflare about reduced Cloudflare Tunnel availability. We monitored the incident and confirmed that our service was not affected. We subsequently improved our detection system to better identify failures with a potential impact on our service.
Our automation system detected the cron error reported by Cloudflare for their Worker service at 20:01 UTC on September 9, 2026. After investigation, this issue did not affect our services. We did find that while our monitoring system correctly reported the upstream error, it failed to provide effective and continuous automated monitoring for it; this issue has now been resolved.