Bridge Nodes

Bridge nodes are the endpoints of the Flashback Network, that give access to the different supported APIs.

For testing purposes only, Flashback has deployed bridge nodes in the following providers and regions for testing purposes. Flashback will offer the capacity to users to deploy their own Flashback Bridge Nodes in their Cloud tenants to avoid excessive egress costs.

---

Deployed Public Bridge Nodes by Flashback

Endpoint Information

Use the following URL pattern to reach any Bridge Node:

https://<api>-<region>-<provider>.flashback.tech

• <api>

  • s3 (for S3-compatible access)

  • gcs (for GCS-compatible access)

  • blob (for Azure Blob access)

• <region>

  • us-east-1

  • eu-central-1

• <provider>

  • aws

  • gcp

  • azure

Examples (region = us-east-1, provider = aws):

• S3 API: https://s3-us-east-1-aws.flashback.tech

• GCS API: https://gcs-us-east-1-aws.flashback.tech

• Blob API: https://blob-us-east-1-aws.flashback.tech

Endpoint Data

Because latency is typically lowest when your Bridge Node is both geographically close and on the same cloud provider as your bucket, it’s best to connect to the node that gives you the fastest response. To help you choose, each Bridge Node publishes real-time stats in the Storage Bucket details view:

• Status

  • ⏺ Online (e.g. “Online 12 ms”) – the node is up and responding in the shown time.

  • ⏺ Disconnected – the node attempted authentication but received an unauthorized error.

  • ⏺ Offline – the node cannot reach the bucket endpoint at all/

• Latency Measured in milliseconds by issuing a HeadBucket request against your bucket and timing the round-trip.