Is Sekoia FRA1 down?

Last checked 8m ago
Current status
Sekoia FRA1 is up

No incidents right now.

Get alerts when Sekoia FRA1 breaks →

Free · no credit card

Official status page: https://status.fra1.sekoia.io · Polled every 5 minutes · 12 components tracked

Real-time Sekoia FRA1 status, recent outages, and incident history — pulled directly from Sekoia FRA1's official status page at https://status.fra1.sekoia.io every 5 minutes. Pingoru tracks 12 Sekoia FRA1 services and has captured 17 incidents in the last 90 days (95.23% uptime). Get email, Slack, Discord, or webhook alerts the moment Sekoia FRA1 reports a new incident — free for 5 monitors, no credit card.

Users who monitor Sekoia FRA1 also follow these Security services: Duo Security LastPass 1Password Barracuda Rapid7 Palo Alto Networks KnowBe4 Incapsula SentinelOne Keeper View all 6,000+ providers
Sekoia FRA1 uptime 95.23% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Slowness on webapp
    Resolved 2h 23m
    Started Apr 27, 2026, 09:32 AM UTC · Resolved Apr 27, 2026, 11:55 AM UTC
    Web application
    2 updates · show timeline
    • monitoring · Apr 27, 2026, 09:32 AM UTC

      We are currently experiencing slowness on some pages due to one of our components being overloaded. A fix has been applied by our team and performances are coming back up. We are still investigating on the root cause and working on improving performances and latency. We will keep you updated

    • resolved · Apr 27, 2026, 11:55 AM UTC

      Response time were back to normal at 11:25 CEST and are stable since. This incident is over. Thank you for your patience.

    Latest: Response time were back to normal at 11:25 CEST and are stable since. This incident is over. Thank you for your patience.

  2. Event indexation delay
    Resolved 16h 51m
    Started Apr 24, 2026, 03:59 PM UTC · Resolved Apr 25, 2026, 08:50 AM UTC
    Event storage
    4 updates · show timeline
    • identified · Apr 24, 2026, 03:59 PM UTC

      Today at 12:38 CEST, we have started to progressively deploy our detection engine. Unfortunately, due to a misconfiguration, some events were not indexed into our storage engine, but all events were processed and related alerts were raised. The proportion of non-indexed events increased gradually. This issue was identified at 16:40 CEST and a fix was deployed around 17:00 CEST. We are now working to fix the situation and ensure that all missed events will be correctly pushed to the storage engine. During the issue, the detection engines continued to work as expected and alerts (including their related events) were correctly raised. All events related to alerts were also correctly indexed into our storage engine.

    • identified · Apr 24, 2026, 04:58 PM UTC

      Our team is currently deploying a fix in order to index the missed events into the storage engine. Be aware that the process is expected to cause duplicates of some events that were already pushed. Thanks for your patience.

    • monitoring · Apr 24, 2026, 06:16 PM UTC

      The fix has been deployed and missed events are currently being indexed into our storage engine. We will continue to inform you on the progress.

    • resolved · Apr 25, 2026, 08:50 AM UTC

      All missed events were correctly pushed to our storage engine during the night. This incident is now over. Thank you for your patience throughout this incident.

    Latest: All missed events were correctly pushed to our storage engine during the night. This incident is now over. Thank you for your patience throughout this incident.

See the full Sekoia FRA1 outage history

15 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 7 incidents
  • Slowness on webapp Resolved
    Started Apr 27, 2026, 09:32 AM UTC · Resolved Apr 27, 2026, 11:55 AM UTC · 2h 23m
  • Event indexation delay Resolved
    Started Apr 24, 2026, 03:59 PM UTC · Resolved Apr 25, 2026, 08:50 AM UTC · 16h 51m
  • Event storage cluster instability Resolved
    Started Apr 22, 2026, 08:54 AM UTC · Resolved Apr 22, 2026, 03:43 PM UTC · 6h 48m
  • Event ingestion delays Resolved
    Started Apr 16, 2026, 03:16 PM UTC · Resolved Apr 16, 2026, 06:41 PM UTC · 3h 25m
  • Degraded playbook automation Resolved
    Started Apr 15, 2026, 07:57 AM UTC · Resolved Apr 15, 2026, 04:46 PM UTC · 8h 48m
  • Assets management Resolved
    Started Apr 08, 2026, 09:15 AM UTC · Resolved Apr 08, 2026, 12:07 PM UTC · 2h 51m
  • Investigating ingestion delays Resolved
    Started Apr 04, 2026, 09:00 PM UTC · Resolved Apr 04, 2026, 10:50 PM UTC · 1h 50m

See Sekoia FRA1 in your Pingoru dashboard

Monitor Sekoia FRA1 alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Sekoia FRA1 to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Sekoia FRA1 incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Sekoia FRA1 or see every provider at once.

Maintenance calendar

Scheduled Sekoia FRA1 maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Sekoia FRA1 status change, one inbox

Pingoru watches Sekoia FRA1's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Sekoia FRA1 reports on 12 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Sekoia FRA1 alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Sekoia FRA1 maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Sekoia FRA1 services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Sekoia FRA1 from the same account, with per-user notification preferences for any monitor.

Get notified on Sekoia FRA1 status changes

Pingoru watches Sekoia FRA1's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Sekoia FRA1 free

Monitor Sekoia FRA1 along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Sekoia FRA1 and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Sekoia FRA1 uptime & incident history

See 90 days of Sekoia FRA1 uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Sekoia FRA1 uptime history

Frequently asked questions

What is Sekoia FRA1's uptime?
Over the last 90 days, Sekoia FRA1 reported 95.23% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.fra1.sekoia.io — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Sekoia FRA1's uptime history rolling forward in real time.
Has Sekoia FRA1 had outages in 2026?
Yes — Sekoia FRA1 has had 17 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Sekoia FRA1 outage?
The most recent Sekoia FRA1 incident was "Slowness on webapp", which started on April 27, 2026 and was resolved on April 27, 2026. Pingoru captured this directly from https://status.fra1.sekoia.io. See the full incident card above for affected components and the update timeline.
How often does Sekoia FRA1 have outages?
Based on the last 90 days, Sekoia FRA1 averages 5.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Sekoia FRA1's status page?
Sekoia FRA1's official status page is https://status.fra1.sekoia.io. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Sekoia FRA1 down right now?
Sekoia FRA1 is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Sekoia FRA1 reports a change. Current status is based on 12 tracked services.
How does Pingoru know if Sekoia FRA1 is down?
We read https://status.fra1.sekoia.io directly, using Sekoia FRA1's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Sekoia FRA1 has an outage?
Create a free Pingoru account and add Sekoia FRA1 as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Sekoia FRA1's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Sekoia FRA1 incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Sekoia FRA1 issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Sekoia FRA1 status?
We use Sekoia FRA1's own status page at https://status.fra1.sekoia.io. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Sekoia FRA1 components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Sekoia FRA1's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Sekoia FRA1 free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →