Incident History

Jan 07, 2026
1. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  23:02 CET
2. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  23:01 CET
3. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  09:32 CET
4. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  09:31 CET
Jan 06, 2026
1. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  13:11 CET
2. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  13:10 CET
Jan 02, 2026
1. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  16:30 CET
2. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  16:13 CET
3. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  16:10 CET
4. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  15:00 CET
5. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  14:54 CET
6. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  14:49 CET
7. api.charlycares.com/api/v2/translations/nl_nl has recovered.
  14:15 CET
8. api.charlycares.com/api/v2/translations/nl_nl appears to be down.
  14:14 CET