EN
BIMcloud SaaS tenants are assigned to a Google Cloud Platform region based on country of purchase, with no option to select or request a different region. Graphisoft's own documentation acknowledges that latency directly impacts Teamwork performance, particularly Send & Receive operations, and directs users to verify their latency using GCPing.com before committing to SaaS. Reference:
We followed that recommendation. The results, measured from Costa Rica using GCPing.com, show the following:
São Paulo (southamerica-east1), which is the assigned region for Costa Rica: 180ms South Carolina (us-east1), the best performing region from our location: 85ms North Virginia (us-east4): 93ms Dallas (us-south1): 108ms
São Paulo is not only the worst performing region in the Americas from Costa Rica, it ranks on par with European cities including London, Madrid, Paris, and Belgium. It performs worse than every US region by a significant margin, and it is geographically further from Costa Rica than multiple US options.
Graphisoft's own network requirements documentation states that slow round-trips significantly affect operations requiring multiple packet exchanges between client and server, specifically naming Send & Receive. At 180ms base latency, every Teamwork operation accumulates this penalty across multiple round-trips, making daily Teamwork use genuinely impractical.
Notably, Graphisoft does not publish a maximum acceptable latency threshold anywhere in the connection test documentation. Users are directed to check their latency without being given a pass or fail benchmark. This means firms in affected regions can unknowingly purchase Collaborate subscriptions, complete the recommended connection test, and still have no basis to evaluate whether their assigned region is acceptable.
The request has two parts.
First, publish a clear maximum acceptable latency threshold in the connection test documentation so that firms can make an informed purchasing decision before committing to a subscription.
Second, allow tenant region selection at purchase, or at minimum allow firms to request reassignment to the lowest-latency available region. Locking tenant assignment to country of purchase without any recourse is not acceptable when the assigned region demonstrably fails to support the product's core workflow.
This affects all of Central America and likely other Latin American countries facing similar routing. It is a verifiable, measurable infrastructure gap that makes a paid feature non-functional for an entire region, and it directly contradicts the product promise of seamless cloud collaboration regardless of location.
4 Comments
Open