System status.
Current availability and recent service checks.
Checking our services.
Current results will appear here in a moment.
- Services operational
- — / 6
- Waiting for checks
- Average check time
- — ms
- Across completed checks
- Needs attention
- —
- Waiting for checks
Our services
Select a service for check detailsWebsiteRailbed’s public website — Checking
What we check
Checks that the website’s published HTML is available.
Latest result
Waiting for the first check.
Merchant dashboardYour account and payment workspace — Checking
What we check
Checks the sign-in application and its data connection. Account sign-in is not exercised.
Latest result
Waiting for the first check.
Hosted checkoutPayment links and checkout pages — Checking
What we check
Checks the checkout application and its data connection. No payment is created or charged.
Latest result
Waiting for the first check.
Merchant APIThe connection between Railbed and your store — Checking
What we check
Checks the API runtime and access to payment, checkout and API-key storage. Authenticated requests are not exercised.
Latest result
Waiting for the first check.
Card routingAvailable routes for card payments — Checking
What we check
Checks that at least one supported card route is available. Inactive options are excluded by routing. The provider feed refreshes every five minutes; buyer eligibility, handoffs, card approvals and settlement are not tested.
Latest result
Waiting for the first check.
DocumentationGuides and developer reference — Checking
What we check
Checks that the documentation’s published HTML is available.
Latest result
Waiting for the first check.
Recent checks
The last 30 checks received by this browser.
History stays on this device. Only checks received while this page is open are recorded; this is not global uptime.
How we check our services
Checks run when this page requests an update, with results shared for up to 30 seconds. This page refreshes every minute while visible and online. Card-provider availability is refreshed every five minutes.
These are availability and readiness checks. They do not make card payments, verify sign-in, deliver merchant webhooks or confirm settlement. Timings measure the checks, not the time to complete a payment. Slow means a page check took over 2.5 seconds or a data check took over 1.5 seconds. A failed service response is unavailable; a check we cannot verify is unknown. A result more than two minutes old is shown as unknown.
You can also read the latest results as JSON.