Incident History

Back to status page

Aug 26, 2026
1. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  03:36 CEST
2. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  03:35 CEST
Aug 25, 2026
1. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  13:15 CEST
2. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  13:13 CEST
Aug 24, 2026
1. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  21:04 CEST
2. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  21:02 CEST
3. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  19:44 CEST
4. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  19:43 CEST
Aug 23, 2026
1. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  16:31 CEST
2. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  16:29 CEST
3. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  16:23 CEST
4. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  16:21 CEST
Aug 20, 2026
1. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  11:54 CEST
2. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  11:53 CEST
Aug 18, 2026
1. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  15:15 CEST
2. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  15:14 CEST
Aug 13, 2026
1. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  12:12 CEST
2. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  12:11 CEST
Aug 09, 2026
1. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  23:30 CEST
2. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  23:29 CEST
3. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  23:14 CEST
4. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  23:05 CEST
Aug 08, 2026
1. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  21:58 CEST
2. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  21:55 CEST
3. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  13:53 CEST
4. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  13:52 CEST

Incident History

api.charlycares.com/api/v2/translations/nl_nl has recovered.

api.charlycares.com/api/v2/translations/nl_nl appears to be down.

api.charlycares.com/api/v2/translations/nl_nl has recovered.

api.charlycares.com/api/v2/translations/nl_nl appears to be down.

api.charlycares.com/api/v2/translations/nl_nl has recovered.

api.charlycares.com/api/v2/translations/nl_nl appears to be down.

api.charlycares.com/api/v2/translations/nl_nl has recovered.

api.charlycares.com/api/v2/translations/nl_nl appears to be down.

api.charlycares.com/api/v2/translations/nl_nl has recovered.

api.charlycares.com/api/v2/translations/nl_nl appears to be down.

api.charlycares.com/api/v2/translations/nl_nl has recovered.

api.charlycares.com/api/v2/translations/nl_nl appears to be down.

api.charlycares.com/api/v2/translations/nl_nl has recovered.

api.charlycares.com/api/v2/translations/nl_nl appears to be down.

api.charlycares.com/api/v2/translations/nl_nl has recovered.

api.charlycares.com/api/v2/translations/nl_nl appears to be down.

api.charlycares.com/api/v2/translations/nl_nl has recovered.

api.charlycares.com/api/v2/translations/nl_nl appears to be down.

api.charlycares.com/api/v2/translations/nl_nl has recovered.

api.charlycares.com/api/v2/translations/nl_nl appears to be down.

api.charlycares.com/api/v2/translations/nl_nl has recovered.

api.charlycares.com/api/v2/translations/nl_nl appears to be down.

api.charlycares.com/api/v2/translations/nl_nl has recovered.

api.charlycares.com/api/v2/translations/nl_nl appears to be down.

api.charlycares.com/api/v2/translations/nl_nl has recovered.

api.charlycares.com/api/v2/translations/nl_nl appears to be down.