Novamag - Notice history

All systems operational

Note that some aspects of Novamag depend on third-party systems which may have their own outages. While we try to update this page when we learn about outages in systems that we depend on, the status pages for the other system may be updated more quickly. These include:

Website - Operational

100% - uptime
01 Jan 1788 · 100.0%01 Feb · 100.0%31 Mar · 100.0%

Previous page

Next page

01 Jan 1788
01 Feb 1788
31 Mar 1788

Frontend - Operational

100% - uptime
01 Jan 1788 · 100.0%01 Feb · 100.0%31 Mar · 100.0%

Previous page

Next page

01 Jan 1788
01 Feb 1788
31 Mar 1788

Backend - Operational

100% - uptime
01 Jan 1788 · 100.0%01 Feb · 100.0%31 Mar · 100.0%

Previous page

Next page

01 Jan 1788
01 Feb 1788
31 Mar 1788

API - Operational

100% - uptime
01 Jan 1788 · 100.0%01 Feb · 100.0%31 Mar · 100.0%

Previous page

Next page

01 Jan 1788
01 Feb 1788
31 Mar 1788

Database - Operational

100% - uptime

Cache - Operational

Medias - Operational

Videos - Operational

Videos - Transcoding Service - Operational

Fonts - Operational

Notice history

01 Sep 2025

Frontend isn't accessible at the moment (automated)
  • Resolved
    Resolved

    Frontend is now operational! This update was created by an automated monitoring service.

  • Investigating
    Investigating

    Frontend cannot be accessed at the moment. This incident was created by an automated monitoring service.

Frontend isn't accessible at the moment (automated)
  • Resolved
    Resolved

    Frontend is now operational! This update was created by an automated monitoring service.

  • Investigating
    Investigating

    Frontend cannot be accessed at the moment. This incident was created by an automated monitoring service.

Frontend isn't accessible at the moment (automated)
  • Resolved
    Resolved

    Frontend is now operational! This update was created by an automated monitoring service.

  • Investigating
    Investigating

    Frontend cannot be accessed at the moment. This incident was created by an automated monitoring service.

Frontend isn't accessible at the moment (automated)
  • Resolved
    Resolved

    Frontend is now operational! This update was created by an automated monitoring service.

  • Investigating
    Investigating

    Frontend cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 Aug 2025

Frontend isn't accessible at the moment (automated)
  • Resolved
    Resolved

    Frontend is now operational! This update was created by an automated monitoring service.

  • Investigating
    Investigating

    Frontend cannot be accessed at the moment. This incident was created by an automated monitoring service.

Frontend isn't accessible at the moment (automated)
  • Resolved
    Resolved

    Frontend is now operational! This update was created by an automated monitoring service.

  • Investigating
    Investigating

    Frontend cannot be accessed at the moment. This incident was created by an automated monitoring service.

Website isn't accessible at the moment (automated)
  • Resolved
    Resolved

    Website is now operational! This update was created by an automated monitoring service.

  • Investigating
    Investigating

    Website cannot be accessed at the moment. This incident was created by an automated monitoring service.

API isn't accessible at the moment (automated)
  • Resolved
    Resolved

    API is now operational! This update was created by an automated monitoring service.

  • Investigating
    Investigating

    API cannot be accessed at the moment. This incident was created by an automated monitoring service.

Frontend isn't accessible at the moment (automated)
  • Resolved
    Resolved

    Frontend is now operational! This update was created by an automated monitoring service.

  • Investigating
    Investigating

    Frontend cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 Jul 2025

API isn't accessible at the moment (automated)
  • Resolved
    Resolved

    API is now operational! This update was created by an automated monitoring service.

  • Investigating
    Investigating

    API cannot be accessed at the moment. This incident was created by an automated monitoring service.

API isn't accessible at the moment (automated)
  • Resolved
    Resolved

    API is now operational! This update was created by an automated monitoring service.

  • Investigating
    Investigating

    API cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 Jul 2025 to 01 Sep 2025

Next