Support
When a sync looks slow or a webhook is late, the status page tells you whether it's PropSocket or something on your end — before you open a ticket. Here's how to read it.
What we track
We report on each part of the platform on its own, so a hiccup in one place doesn't make you guess about the rest. If your dashboard loads fine but a sync is stuck, the status page shows you exactly that.
The /v1 endpoints your systems call to read your Common Data Model data. If this is degraded, your reads may be slow or failing.
The signed notifications we push to your endpoints when your data changes. If this is degraded, deliveries may be delayed or retrying.
The workers that pull data from each connected system, tracked per PMS — Entrata today, more as they launch. An issue with one connector won't be hidden behind another.
The tenant dashboard where you manage integrations, view sync status, and rotate keys. If this is down, the API and syncs can still be running fine underneath.
Incident states
During an incident, the status page moves through four states. Here's what each one tells you about where we are.
Investigating
We've seen a problem and confirmed it's real, but we don't yet know the cause. We're actively looking. Posting this fast is the point — you shouldn't have to wonder.
Identified
We know what's causing it and we're working on the fix. The update will say what's affected and, when we can estimate it, what to expect next.
Monitoring
The fix is in place and things look healthy, but we're watching to make sure it holds before we call it done. If anything affected you was queued — like delayed webhooks — this is usually when it catches up.
Resolved
The incident is over and the component is healthy. For larger incidents, a postmortem follows — see ourincident communication policyfor when and what.
Don't wait to find out
Refreshing a page during an outage is no one's idea of a good time. Subscribe once and get notified the moment a component changes state.
If everything's green and your integration still isn't behaving, that's worth a message. Have your request ID handy and we'll dig in — within one business day.