LIVE SERVICE HEALTH

Production, measured from where you are.

This page sends real requests from your browser to the SeatLayer production API. See response time, serving edge and measurement history—not a cached green badge.

LIVE PROBE · YOUR NETWORK · PRODUCTION ORIGIN · NO SYNTHETIC UPTIME CLAIM
BROWSER → PRODUCTION API● CHECKING
ROUND TRIP— ms
SERVING EDGE
LAST CHECK
Live probeFrom your browser to production
4 surfacesAPI, app, docs and SDK
No cached badgeFresh API request
Public contactFor regional issues
SERVICE SURFACES

One measured origin. Three directly inspectable surfaces.

The API state below comes from the live browser probe. Dashboard, documentation and SDK links open their production surfaces directly.

APIapi.seatlayer.io
checking…
Dashboardapp.seatlayer.io
inspect surface ↗
Docsdocs.seatlayer.io
inspect surface ↗
SDK CDNcdn.seatlayer.io/seatlayer-js@0/seatlayer.js
inspect surface ↗
checkingLast browser probe
HTTPS / WSSEncrypted public surfaces
hello@seatlayer.ioIncident contact

Something look wrong from where you are? Tell us: hello@seatlayer.io

REQUEST PATH

Understand what a healthy buyer journey depends on.

A seat selection crosses a small number of explicit surfaces, each with a narrow responsibility.

Buyer SDKrender + selection
Production APIpublic event routes
Event authorityordered inventory state
Your backendinspect + payment + book
MEASUREMENT TRANSPARENCY

Know what this page proves—and what it does not.

A browser probe is one regional observation. It is useful evidence, not a substitute for complete multi-region monitoring or an SLA report.

MEASURED HERE

Production API reachability

Fresh no-store requests, response status, browser round-trip time and returned serving-edge code.

NOT INFERRED

Linked surfaces are not greenwashed

Dashboard, docs and CDN are presented as direct inspection links unless this browser can verify their status.

SECURITY CONTEXT

Architecture and boundaries

Review tenant isolation, credential placement, webhook delivery and minimal-data design separately.

Open security architecture →
REGIONAL ISSUE REPORTING

Your route can fail while another region looks healthy.

Send the time, country or region, affected surface, browser error and—if visible—the edge code shown above. That gives us a precise starting point without asking for buyer personal data.

INCIDENT CONTACThello@seatlayer.io

Include timestamp, region, affected URL and observed behavior. Never include account secrets, payment information or buyer PII.

Report an operational issue Talk to us