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 2026 · 99.99%01 Feb · 100.0%31 Mar · 99.99%

Previous page

Next page

01 Jan 2026
01 Feb 2026
31 Mar 2026

Frontend - Operational

100% - uptime
01 Jan 2026 · 99.91%01 Feb · 99.79%31 Mar · 99.88%

Previous page

Next page

01 Jan 2026
01 Feb 2026
31 Mar 2026

Backend - Operational

100% - uptime
01 Jan 2026 · 99.97%01 Feb · 100.0%31 Mar · 99.92%

Previous page

Next page

01 Jan 2026
01 Feb 2026
31 Mar 2026

API - Operational

100% - uptime
01 Jan 2026 · 99.97%01 Feb · 100.0%31 Mar · 100.0%

Previous page

Next page

01 Jan 2026
01 Feb 2026
31 Mar 2026

Database - Operational

100% - uptime

Cache - Operational

Medias - Operational

Videos - Operational

Videos - Transcoding Service - Operational

Fonts - Operational

Notice history

01 Mar 2026

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

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

  • Investigating
    Investigating

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

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

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

  • Investigating
    Investigating

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

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

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

  • Investigating
    Investigating

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

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

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

  • Investigating
    Investigating

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

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

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

  • Investigating
    Investigating

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

01 Feb 2026

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.

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 Jan 2026

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.

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 Jan 2026 to 01 Mar 2026

Next