Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Historia awarii Veem

    12 Veem incidents · czerwiec 2019 — official updates, affected components, duration and resolution details.

    Wróć do bieżącego statusu

    planned downtime for db upgrade 9pm-11pm PST

    Początek 16 sierpnia 2025 03:56 UTC · 2h 26m

    Pending
    Dotknięte komponenty
    www.veem.comapps.veem.comapi.veem.com
    1. 16 sierpnia 2025 03:56 UTCinvestigating

      We are currently investigating this issue.

    2. 16 sierpnia 2025 06:22 UTCresolved

      resolved

    DB upgrade in progress

    Początek 16 sierpnia 2025 00:07 UTC · 6h 16m

    Pending
    1. 16 sierpnia 2025 00:07 UTCinvestigating

      We are currently investigating this issue.

    2. 16 sierpnia 2025 06:23 UTCresolved

      resolved

    Login issues

    Początek 5 października 2023 19:20 UTC · 35m

    OutagePoważny incydent
    Dotknięte komponenty
    apps.veem.com
    1. 5 października 2023 19:20 UTCinvestigating

      We are aware of an issue with login to our customer application. We are investigating the cause of the problem.

    2. 5 października 2023 19:54 UTCinvestigating

      The issue is now resolved

    3. 5 października 2023 19:55 UTCresolved

      This incident has been resolved.

    System Outage

    Początek 11 września 2023 12:00 UTC · 9h 46m

    Pending
    Dotknięte komponenty
    apps.veem.comapi.veem.com
    1. 11 września 2023 19:52 UTCinvestigating

      We are experiencing a systemwide outage. We are working with our system providers to investigate the cause.

    2. 11 września 2023 21:45 UTCinvestigating

      We have resolved the outage and the system is now operational.

    3. 11 września 2023 21:47 UTCresolved

      This incident has been resolved.

    Issues with Veem API

    Początek 21 lutego 2023 21:27 UTC · 17h 30m

    IssuesDrobny incydent
    Dotknięte komponenty
    api.veem.com
    1. 21 lutego 2023 21:27 UTCinvestigating

      We are currently investigating this issue.

    2. 21 lutego 2023 21:51 UTCidentified

      The issue has been identified and a fix is being implemented.

    3. 21 lutego 2023 22:16 UTCmonitoring

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

    4. 22 lutego 2023 14:57 UTCresolved

      This incident has been resolved.

    Intermittent Issues with Veem API

    Początek 1 lutego 2023 19:30 UTC · 0m

    Pending
    1. 4 lutego 2023 05:11 UTCresolved

      Veem Public API (api.veem.com) had some intermittent issues between 2:30 PM to 3:30 PM EST. Some customer may have experienced deteriorated performance on the Veem Customer App (apps.veem.com). The issue has been identified and resolved.

    Operational Issues Due to Cloud Service Provider

    Początek 18 listopada 2022 05:14 UTC · 0m

    Pending
    1. 4 lutego 2023 05:17 UTCresolved

      Veem API (app.veem.com) and Veem Customer App (apps.veem.com) had partial service disruption due to a service outage on our Cloud Service Provider. Users may have experienced performance issues between 2:40 UTC and 6:00 UTC because of the same.

    Operational Issues

    Początek 7 grudnia 2021 17:06 UTC · 8h 18m

    OutagePoważny incydent
    Dotknięte komponenty
    www.veem.comapps.veem.comapi.veem.com
    1. 7 grudnia 2021 17:06 UTCinvestigating

      We are experiencing issues with our services due to issues with our provider. We will keep you updated on the status.

    2. 7 grudnia 2021 18:00 UTCinvestigating

      We rely on Amazon webservices that are experiencing a global outage . We will keep you updated on the status.

    3. 8 grudnia 2021 01:22 UTCinvestigating

      Our services are now back online. We apologize for any inconveniences.

    4. 8 grudnia 2021 01:24 UTCresolved

      This incident has been resolved.

    Outage due to upstream cloud provider

    Początek 17 kwietnia 2020 09:02 UTC · 3h 12m

    OutagePoważny incydent
    Dotknięte komponenty
    apps.veem.comapi.veem.com
    1. 17 kwietnia 2020 10:40 UTCinvestigating

      Veem's applications are being affected by an upstream cloud provider outage by Amazon Web Services. We are monitoring the situation and will provide updates as further information becomes available.

    2. 17 kwietnia 2020 12:13 UTCinvestigating

      AWS has resolved the upstream issue and our application is once again operating as normal.

    3. 17 kwietnia 2020 12:13 UTCresolved

      This incident has been resolved.

    Degraded response times from api.veem.com and apps.veem.com

    Początek 28 grudnia 2019 10:00 UTC · 4h 45m

    OutagePoważny incydent
    1. 28 grudnia 2019 18:11 UTCresolved

      For approximately two hours beginning at 1445 UTC, users may have experienced increased response times from our application and public API. This was due to a DDOS attack directed our services. This was resolved at approximately 1715 UTC and all services are now operating normally.

    External Provider Incident

    Początek 2 lipca 2019 14:15 UTC · 1m

    Pending
    1. 2 lipca 2019 14:15 UTCinvestigating

      Due to an external provider outage, users may not be able to access our website and applications. We are monitoring the situation and will provide an update when the provider outage is resolved.

    2. 2 lipca 2019 14:16 UTCresolved

      This incident is now resolved and service is back to normal.

    External Network Provider Incident

    Początek 24 czerwca 2019 12:10 UTC · 56m

    OutagePoważny incydent
    Dotknięte komponenty
    apps.veem.comapi.veem.com
    1. 24 czerwca 2019 12:10 UTCinvestigating

      Due to an external network provider outage, some users may be unable to access our application. This is sadly beyond our control as it affects multiple regions within our cloud provider.

    2. 24 czerwca 2019 12:11 UTCmonitoring

      We are monitoring connectivity to our application and will update when the external network provider outage has been resolved.

    3. 24 czerwca 2019 13:04 UTCmonitoring

      The external network provider incident has been resolved and our apps are once again reachable as normal.

    4. 24 czerwca 2019 13:06 UTCresolved

      This incident has been resolved.