To create a performance profile in Chrome:
- Right click anywhere on the toolbar in your Gather Space and select Inspect or Inspect Element. The developer console opens.
- In the developer console, open the Performance tab, then select the recording button to start recording performance data.
- Reproduce your performance issue during the recording!
a. You may need to refresh in order to reproduce your issue again - plan ahead and do that before you start recording if necessary.
b. If it’s a transient issue (e.g., after walking out of a meeting and suddenly your performance is terrible for no reason) don’t refresh before recording. - Stop the recording and wait for your performance profile to load.
- Select Save Profile next to the Record button in the console.
- Save the file, then send it to us (or if it's too large to send, upload it somewhere and send us the link).
Some campus and corporate networks, VPNs, and firewalls will by default block traffic for Gather video calls. If you are using a campus or corporate network, VPN or firewall, and are having trouble accessing Gather, you can try the following actions to fix it:
Disable your VPN or Firewall
Visit your VPN provider's support website and try different connection options
Change your connection to a different server or network if your VPN will allow you to do so
Ask your network administrator to unblock the following endpoints, which we use to provide video calls on Gather:
Gather uses several different video backends. To check which video backend your space is using, enter your space and open the debug overlay with ctrl-shift-d or cmd-shift-d. On the left side of the screen, look for the value of the ‘A/V Backend’ field.
Since the backend can occasionally change depending on service availability, you may want to unblock all backends to ensure connectivity.
If your backend is Gather, you need:
Service | Host | Ports | Explanation |
Gather router | router.gather.town | 443 TCP | The router is used for signaling on the Gather video backend. |
Twilio | See Twilio's Knowledgebase for hosts in your region | 443 TCP (TURN TLS) Note that you do not need to allow traffic on UDP ports 10000-60000, we only need the three mentioned ports. | We use Twilio to accommodate firewalls and restrictive networks. Instructions for unblocking their IP addresses in your region are available on Twilio's Knowledgebase. |
If your backend is Livekit, you need:
Service | Host | Ports | Explanation |
LiveKit | gather.livekit.cloud | 443 TCP | This endpoint is used for signaling on the Livekit video backend. |
Twilio | See Twilio's Knowledgebase for hosts in your region | 443 TCP (TURN TLS) Note that you do not need to allow traffic on UDP ports 10000-60000, we only need the three mentioned ports. | We use Twilio to transfer media when behind a firewall or restrictive network. Instructions for unblocking their IP addresses in your region are available on Twilio's Knowledgebase. |
If your backend is Agora, you need:
Service | Host | Ports | Explanation |
Ably | rest.ably.io realtime.ably.io a.ably-realtime.com b.ably-realtime.com c.ably-realtime.com d.ably-realtime.com e.ably-realtime.com | 443 TCP (TLS) | These endpoints are used for signaling on the Agora video backend. |
agoraio.dev | gather.agoraio.dev | 443 TCP (TLS) | Used for connection setup on the Agora video backend. |
Agora Cloud Proxy | See Agora’s documentation for required IPs | 443 TCP (TLS) (required), | The Agora video backend uses Agora Cloud Proxy to transfer media when behind a firewall or restrictive network. See required IPs in Agora’s documentation. |