DE-CIX Bengaluru: operator report
Bengaluru, India · PeeringDB 5045 · ixreport.com/ix/5045/report/
Members of DE-CIX Bengaluru that PeeringDB has wrong, from its IX-F export (8 networks, read 2026-10-08 18:46 UTC), against PeeringDB as of 2026-10-08 18:53 UTC. 7 networks to follow up; 4 with a public PeeringDB contact.
Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.
On your lists, missing from PeeringDB (6)
These networks could add DE-CIX Bengaluru to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS12345 AWS-CLOUD | IX-F | – 10G |
No PeeringDB record |
| AS31399 Mercedes-Benz Group AG | IX-F | – 2 × 10G + 2 × 1G |
Policy: email address (needs JavaScript) |
| AS32934 Meta | IX-F | 151.158.193.5 151.158.193.6 2400:d180:77::5 2400:d180:77::6 2 × 100G |
Policy: email address (needs JavaScript) |
| AS58299 Openfactory GmbH | IX-F | 151.158.193.1 1G |
No public contact |
| AS141566 Gaxiom Networking Solutions | IX-F | 151.158.193.2 2400:d180:77::2 1G |
No public contact |
| AS146919 CtrlS Connect | IX-F | – 10G |
Policy: email address (needs JavaScript) +919154745794 |
Addresses or port speeds that differ (0)
PeeringDB against your IX-F export, for the 2 networks in both. Either the network's PeeringDB record or the export is out of date.
None: every network's addresses and port speed match.
In PeeringDB, not on your lists (1)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.
| Network | In PeeringDB | Contact |
|---|---|---|
| AS9442 DE-CIX Bengaluru Route Servers | 151.158.193.64 151.158.193.65 2400:d180:77::64 2400:d180:77::65 2 × 10G |
Policy: email address (needs JavaScript) |