CRDStatus
SERVICE AVAILABILITY

Every service. A clear picture.

Follow CRD availability, maintenance and incident updates from our team.

Checking services

Automated checks of public service endpoints.

Checking…0/5 services responding
01

CRD portals

Main portal availability

Checking
02

Sign-in

Authentication service availability

Checking
03

Portal data

Data API connectivity

Checking
04

CRD Engine API

Readiness and request processing

Checking
05

Webhooks & sync

Delivery worker activity

Checking

Refreshes every 60 seconds. Checks measure availability, not the success of every operation. Webhook status covers our worker, not receipt by every destination. Scan and removal incidents are reported below.

THE LOG

Incident history

All times UTC
28SEP 2026
Resolved

Infrastructure capacity upgrade

Portal · Sign-in · Data

  1. Completed

    Restart completed. Database, sign-in and Data API health checks are passing again. The increased memory capacity has been verified.

  2. Maintenance

    A capacity upgrade required a restart. The portal and dependent services were temporarily unavailable during the operation.

Resolved

Delayed scheduled scans

Scans · Monitoring

  1. Resolved

    All eligible scans in this batch were verified complete, the last at 14:44 UTC, with no recorded scan errors. Automatic catch-up scheduling is active.

  2. Recovery

    The missed batch was queued again. A check every 15 minutes now recovers missed dispatches without changing each plan’s scan frequency.

  3. Incident

    The daily dispatch failed with a database startup timeout. The missed batch was confirmed during the 11:08 UTC review.

Resolved

Slow or unavailable sign-in

Sign-in · Data

  1. Recovered

    Service recovered after a restart. The sign-in form also now has a request deadline and a clear error message to prevent an indefinite loading state.

  2. Disruption observed

    Logs confirm Data API errors and authentication timeouts. Some customers could not access the portal. The exact start time was not established.

This history starts on 28 September 2026 and contains verified incidents. Earlier periods are not measured here.

Something wrong with your account?

Our team can look into your individual situation.

Contact support