Does gitlab.com support IPv6?
Partly. On November 6, 2026, about.gitlab.com answered over IPv6, but its home page loads from 7 hosts and 1 of them is IPv4-only, so an IPv6-only connection gets the page with those parts missing.
Hosts that block an IPv6-only load
These hosts publish an IPv4 address but no AAAA record. Over an IPv6-only connection the browser cannot fetch anything they serve.
- munchkin.marketo.net — <script src>
Every host the gitlab.com home page loads from
| Host | Protocol | AAAA record |
|---|---|---|
| about.gitlab.comThe page itself | IPv6 | 2606:4700::6812:1d81 |
| munchkin.marketo.net | IPv4 only | — |
| cdn.bizible.com | IPv6 | 2a02:26f0:1380:1f::214:471b |
| cdn.cookielaw.org | IPv6 | 2606:4700::6812:572a |
| cdn.optimizely.com | IPv6 | 2606:4700::6812:4139 |
| geolocation.onetrust.com | IPv6 | 2606:4700:4403::6812:2089 |
| res.cloudinary.com | IPv6 | 2606:4700::6810:4f06 |
Can I reach gitlab.com through an IPv6 proxy?
An IPv6-only route reaches the site but not every resource. Use IPv4, or a plan that falls back to IPv4, when the missing parts matter to you, such as a script that renders prices.
How this was measured
The IPv6 test loaded https://about.gitlab.com/ once on November 6, 2026, read every host the returned HTML asks a browser to fetch, and looked up AAAA and A records for each. Hosts added later by JavaScript are not counted, and other pages on the site can depend on different hosts. Results change as sites move providers.