Schedo.dev Status

The downtime incidents reported by the open status monitoring system commencing May 31 have been determined to be erroneous. An investigation revealed that the monitoring configuration was inadvertently directed toward a legacy API server endpoint rather than the current production infrastructure.

This misconfiguration resulted in false downtime alerts being generated while the primary API services remained fully operational and accessible to users throughout the reported incident period. The monitoring system has since been updated to reflect the correct endpoint configuration.

The downtime incidents reported by the open status monitoring system commencing May 30 have been determined to be erroneous. An investigation revealed that the monitoring configuration was inadvertently directed toward a legacy API server endpoint rather than the current production infrastructure.

This misconfiguration resulted in false downtime alerts being generated while the primary API services remained fully operational and accessible to users throughout the reported incident period. The monitoring system has since been updated to reflect the correct endpoint configuration.

The downtime incidents reported by the open status monitoring system commencing May 29th have been determined to be erroneous. An investigation revealed that the monitoring configuration was inadvertently directed toward a legacy API server endpoint rather than the current production infrastructure.

This misconfiguration resulted in false downtime alerts being generated while the primary API services remained fully operational and accessible to users throughout the reported incident period. The monitoring system has since been updated to reflect the correct endpoint configuration.