Aglebert Service Status

Frontend service status for applications managed by Team Aglebert.

Both APIs and public frontends are included. Most business-critical services should appear at the beginning of this list.

  • 200 OK
    v6
    v4
    h2
    2 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 200 OK
    v6
    v4
    h2
    5 mins
  • 204 No Content
    v6
    v4
    h2
    5 mins
  • 200 OK
    v6
    v4
    h2
    5 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 200 OK
    v6
    v4
    h2
    5 mins
  • 200 OK
    v6
    v4
    h2
    5 mins
  • 200 OK
    v6
    v4
    h2
    5 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 200 OK
    v6
    v4
    h2
    5 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 204 No Content
    v6
    v4
    h2
    10 mins
  • 200 OK
    v6
    v4
    h2
    5 mins
  • 200 OK
    v6
    v4
    h2
    30 mins
  • 200 OK
    v6
    v4
    h2
    5 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 200 OK
    v6
    v4
    h2
    5 mins
  • 200 OK
    v6
    v4
    h2
    10 mins
  • 204 No Content
    v6
    v4
    h2
    10 mins