Syncpoint sits between your build pipeline and your users. Assets are published once, addressed by content hash, and served from the nearest edge location. Telemetry travels the other way on the same connection pool.
Every published asset is written to an immutable path. Because the hash changes when the content changes, caches never need invalidating and a rollback is just a redeploy of an earlier manifest.
Client SDKs buffer events locally and flush on an interval. If the network is unavailable the buffer persists to local storage and drains when connectivity returns. Duplicate suppression happens server side.
| Region | Code | Status |
|---|---|---|
| London | uk-lon-1 | Available |
| Frankfurt | eu-fra-1 | Available |
| Virginia | us-east-1 | Available |
| Singapore | ap-sin-1 | Waitlist |
Engineering support is available on business plans. Response targets are one business day for standard issues and four hours for delivery incidents.