SEO Crawler status page
  • Status
  • Events
  • Monitors
SEO Crawler
We continuously scan your domains to detect broken links, track SSL certificate health, and identify orphan pages. Automated crawls and AI-powered insights ensure your websites remain reliable, fast, and error-free. This status page provides real-time updates on the health and performance of our monitoring services.
Back
Dec 12, 2025
2 months ago
Status Page Display Issue
Crawler EnginePayment PortalData StorageNotificationsRest API
Resolved · December 12 at 7:39 AM (in 7 minutes)

Post-Mortem: Status Page Display Incident

Date: 12/12/25 Duration: 8 Hours Severity: Low (Display / Monitoring only)
Affected Component: Public Status Page


Summary

An issue was identified where the public status page incorrectly displayed the application as offline. This was caused by a firewall configuration blocking outbound server status checks. The incident did not impact the availability or functionality of the application itself—only the accuracy of the status page.

All core systems remained fully operational throughout the incident.


Impact

  • The public status page showed degraded or offline status.
  • No customer-facing services, APIs, or internal systems were affected.
  • No data loss or service interruption occurred.

Root Cause

A firewall rule was incorrectly configured, resulting in server status and health-check requests being blocked. This prevented the status monitoring service from receiving valid responses, causing a false offline indication.


Detection

The issue was detected via internal review after discrepancies were noticed between operational metrics and the public status page display.


Resolution

  • Firewall rules were updated to allow required server status and health-check requests.
  • Monitoring was revalidated to ensure correct connectivity.
  • The system is currently being observed to confirm consistent and accurate reporting.

Preventative Measures

To prevent similar issues in the future, we are implementing the following actions:

  • Review and document firewall rules related to monitoring and observability.
  • Introduce automated alerts for failed health-check responses that do not correlate with internal uptime metrics.
  • Add a secondary validation check for status page reporting.

Lessons Learned

  • Monitoring and observability components should be treated as critical infrastructure.
  • Changes to security controls (such as firewall rules) must include validation against monitoring dependencies.
  • Clear separation between service availability and status reporting helps reduce confusion during incidents.

Current Status

All systems are operational.
The firewall update has been applied, and we are monitoring results to ensure continued stability and accuracy.


If you have any questions regarding this incident, please contact our support team.

Identified · December 12 at 7:38 AM (1 minute earlier)

We have updated our firewall configuration and are currently awaiting confirmation of the results.

The earlier issue caused server status requests to be blocked, which may have incorrectly shown the application as offline. All systems remain fully operational.

We are monitoring the situation closely and will provide further updates once the fix has been fully validated.

Identified · December 12 at 7:32 AM (5 minutes earlier)

We are aware of an issue currently affecting our status page.

Due to a firewall configuration error, server status requests are being blocked, which may incorrectly indicate that the application is offline. Please be assured that all systems are fully operational.

Our team is actively working on a fix and will provide updates as soon as the issue is resolved.

powered by openstatus.dev