NeoRank
Analizar mi sitio web

Estado del servicio

Este contenido solo está disponible en inglés por el momento.

NeoRank service status

All systems operational

Last check

Continuous measurements since 5 Oct 2026 · one check a minute

Components

Measured daily availability over 90 days (UTC days). Grey: no measurement that day.

  • Website

    Full load of the public home page.

    Operational
    24 h
    100%
    7 d
    100% · over 27 h measured
    30 d
    100% · over 27 h measured
    90 d
    100% · over 27 h measured
    Latency 24 h
    p50 186 ms · p95 284 ms

  • API

    API health endpoint, response checked.

    Operational
    24 h
    100%
    7 d
    100% · over 27 h measured
    30 d
    100% · over 27 h measured
    90 d
    100% · over 27 h measured
    Latency 24 h
    p50 93 ms · p95 130 ms

  • Database

    Minimal read query, round-trip time.

    Operational
    24 h
    100%
    7 d
    100% · over 27 h measured
    30 d
    100% · over 27 h measured
    90 d
    100% · over 27 h measured
    Latency 24 h
    p50 71 ms · p95 88 ms

  • Analysis queue

    A consumer is attached and the oldest waiting analysis has not waited too long.

    Operational
    24 h
    100%
    7 d
    100% · over 27 h measured
    30 d
    100% · over 27 h measured
    90 d
    100% · over 27 h measured
    Latency 24 h
    p50 0 ms · p95 0 ms

  • AI engines

    AI engines verified and available in the catalogue (no provider is called).

    Operational
    24 h
    100%
    7 d
    100% · over 27 h measured
    30 d
    100% · over 27 h measured
    90 d
    100% · over 27 h measured
    Measure
    7 verified engine(s)

  • Google connectors (APIs and syncs)

    Reachability of the Google APIs the connectors depend on (a request with no key and no customer data to a public Google endpoint, every minute). From 5 Search Console / Analytics syncs in the hour, all customers together, the failure rate is published too; Google access a customer let expire or revoked is left out (it concerns their account, not a NeoRank incident).

    Operational
    24 h
    100%
    7 d
    100% · over 27 h measured
    30 d
    100% · over 27 h measured
    90 d
    100% · over 27 h measured
    Latency 24 h
    Google APIs p50 62 ms

Response time

Median (p50) and 95th percentile (p95) per interval, measured by the probes. The amber band marks the slowdown threshold.

Analysis queue

Wait of the oldest analysis before it starts (p95 per interval). A rising wait signals slower processing.

Incident history

Detected automatically: three consecutive failed or too-slow checks. Last 90 days.

No incident measured on the period (measurements since 5 Oct 2026).

Methodology

What is measured

  • Website — Full load of the public home page.
  • API — API health endpoint, response checked.
  • Database — Minimal read query, round-trip time.
  • Analysis queue — A consumer is attached and the oldest waiting analysis has not waited too long.
  • AI engines — AI engines verified and available in the catalogue (no provider is called).
  • Google connectors (APIs and syncs) — Reachability of the Google APIs the connectors depend on (a request with no key and no customer data to a public Google endpoint, every minute). From 5 Search Console / Analytics syncs in the hour, all customers together, the failure rate is published too; Google access a customer let expire or revoked is left out (it concerns their account, not a NeoRank incident).

How and from where

A probe inside the platform checks each component once a minute, with no third-party monitoring service; only the “Google connectors” component calls Google, on a public endpoint, with no key and no customer data. Results are kept 48 h at one-minute resolution, 8 days in 5-minute buckets and 90 days hourly. Times are shown in UTC.

When a measurement is impossible (for example a page behind authentication the probe cannot pass), nothing is recorded: a missing measurement never counts as availability, nor as an outage. The sync failure rate is only published from 5 syncs in the hour, all customers together, and is never tied to an account. This page publishes no infrastructure detail.

Definitions

Operational
Recent checks succeed within the thresholds.
Degraded
Three consecutive checks too slow (beyond the slowdown threshold) or partly failing.
Outage
Three consecutive failed checks.
No measurement
No check for more than 3 minutes, or measurement impossible.

Availability = successful checks (including degraded) ÷ checks performed. First measurement: 5 Oct 2026, 20:22 UTC.

Subscribe to incidents (Atom feed)