Globe Telecom: PeeringDB fix list
AS4775 · peeringdb.com/net/1919
6 things to fix in Globe Telecom's PeeringDB record, from what its exchanges publish: 1 to add, 4 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Globe Telecom's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (1)
On the exchange's own member list, but not in Globe Telecom's PeeringDB record. Add one entry per connection with these values.
-
IPv4 112.137.26.166 IPv6 2407:b140:ae5::a500:4775:1 Speed 100000 Mbps (100G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Correct these entries (4)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 103.247.139.44: set Speed to 100000 (100G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 112.137.24.84: set Speed to 100000 (100G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 1G 200G - In the entry with IPv4 80.81.195.224: set Speed to 200000 (200G) (now 1000).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 103.104.19.22 103.104.19.22 103.104.19.80 IPv6 address missing from PeeringDB 2401:fdc0::4775:1 2401:fdc0::4775:1 2401:fdc0::4775:2 Port speed differs 100G 2 × 100G + 10G - Add an entry: IPv4 103.104.19.80, IPv6 2401:fdc0::4775:2, speed 100000 (100G), RS peer yes.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Globe Telecom has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
Any2West Los Angeles and Silicon Valley, United States · PeeringDB 142Not on its website members listIPv4 206.72.210.197 IPv6 2001:504:13::197 Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/4775/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.