SysAid - Notice history

100% - uptime

INST03US - Virginia - Operational

100% - uptime
2022-05-01 · 99.91%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST04US - Virginia - Operational

100% - uptime
2022-05-01 · 99.91%-06-01· 99.95%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST05US - Virginia - Operational

100% - uptime
2022-05-01 · 99.91%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST06US - Virginia - Operational

100% - uptime
2022-05-01 · 99.91%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST07US - Oregon - Operational

100% - uptime
2022-05-01 · 99.91%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST08US - Oregon - Operational

100% - uptime
2022-05-01 · 99.91%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST09US - Oregon - Operational

100% - uptime
2022-05-01 · 99.91%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST64US - Virginia - Operational

100% - uptime
2022-05-01 · 100.0%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST67US - Virginia - Operational

100% - uptime
2022-05-01 · 100.0%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST72US - Oregon - Operational

100% - uptime
2022-05-01 · 100.0%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST73US - Oregon - Operational

100% - uptime
2022-05-01 · 100.0%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST74US - Oregon - Operational

100% - uptime
2022-05-01 · 100.0%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST80CA - Canada - Operational

100% - uptime
2022-05-01 · 99.91%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31
100% - uptime

INST15EU - Dublin - Operational

100% - uptime
2022-05-01 · 100.0%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST16EU - Dublin - Operational

100% - uptime
2022-05-01 · 100.0%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST17EU - Dublin - Operational

100% - uptime
2022-05-01 · 100.0%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST18EU - Dublin - Operational

100% - uptime
2022-05-01 · 100.0%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST19EU - Frankfurt - Operational

100% - uptime
2022-05-01 · 100.0%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

INST21EU - Dublin - Operational

100% - uptime
2022-05-01 · 100.0%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31
100% - uptime

INST13AU - Melbourne - Operational

100% - uptime
2022-05-01 · 100.0%-06-01· 100.0%-07-31· 100.0%
2022-05-01
2022-06-01
2022-07-31

Third Party: OpenAI → API - Operational

100% - uptime

Pinecone us-east-1-aws - Operational

Pinecone us-west1-gcp - Operational

Pinecone northamerica-northeast1-gcp - Operational

100% - uptime

Third Party: Amazon Web Services → AWS route53 - Operational

Notice history

2022-07-01

No notices reported this month

2022-06-01

2022-05-01

Login issues caused by Certificate Error in Browser
  • Update
    Update

    On 2 May 2022, between 19:50-22:00 UTC, some customers using the Google Chrome browser experienced certificate errors that prevented users from logging in to their system.  ‌ It appears that this issue affected many different services across the globe. It originated with [changes to Google’s infrastructure](https://groups.google.com/a/chromium.org/g/ct-policy/c/P3_hj9QmsLc) and process of evaluating valid certificates. To quickly mitigate the issue we implemented new certificates from a different provider and have verified that our customers are no longer experiencing the errors. ‌ We resolved the error within three hours of notification. SysAid will continue to investigate further to mitigate future incidents, and remain committed to providing our customers with a stable and secure platform

  • Resolved
    Resolved

    This incident has been resolved.

  • Update
    Update

    We are continuing to monitor for any further issues.

  • Update
    Update

    We are continuing to monitor for any further issues.

  • Update
    Update

    We are continuing to monitor for any further issues.

  • Update
    Update

    We are continuing to monitor for any further issues.

  • Update
    Update

    Monitoring - A fix has been implemented and we are monitoring the results.

  • Monitoring
    Monitoring

    A fix has been implemented and we are monitoring the results.

  • Update
    Update

    We are continuing to investigate this issue.

  • Update
    Update

    We are continuing to investigate this issue.

  • Update
    Update

    We are continuing to investigate this issue.

  • Investigating
    Investigating

    We are currently investigating this issue.

2022-05-01 to 2022-07-01

Next