VeriSign Global Registry Services
AS26415
VeriSign
Tools: Where can I peer with VeriSign Global Registry Services? · Where should VeriSign Global Registry Services peer next? · Compare VeriSign Global Registry Services with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
16 things to fix in VeriSign Global Registry Services's PeeringDB record, from what its exchanges publish: 3 to add, 12 to correct, 1 to check. As of 2026-11-19 12:40 UTC.
Make the changes on VeriSign Global Registry Services'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 (3)
On the exchange's own member list, but not in VeriSign Global Registry Services's PeeringDB record. Add one entry per connection with these values.
-
DE-CIX Richmond Ashland, United States · PeeringDB 1002From its IX-F export and website members list
IPv4 206.53.137.32 IPv6 2001:504:44::672f:0:1 Speed 10000 Mbps (10G) RS peer Yes -
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 206.83.12.9 IPv6 2001:504:98::9 Speed Not published RS peer Not published
Correct these entries (12)
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 1G 10G - In the entry with IPv4 193.37.144.19: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has IPv6 address differs 2001:43f8:9c1:1::200 2001:43f8:9c1:1:0:a502:6415:1 - In the entry with IPv4 196.223.38.200: set IPv6 to 2001:43f8:9c1:1:0:a502:6415:1 (now 2001:43f8:9c1:1::200).
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 2G - In the entry with IPv4 193.178.185.119: set Speed to 2000 (2G) (now 1000).
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 10G - In the entry with IPv4 203.159.68.9: set Speed to 10000 (10G) (now 1000).
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 100G - In the entry with IPv4 27.106.192.3: set Speed to 100000 (100G) (now 1000).
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 2 × 1G 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 10G - In the entry with IPv4 196.60.70.93: set Speed to 10000 (10G) (now 1000).
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 10G - In the entry with IPv4 196.60.8.93: set Speed to 10000 (10G) (now 1000).
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 10G - In the entry with IPv4 195.130.211.17: set Speed to 10000 (10G) (now 1000).
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 10G - In the entry with IPv4 206.197.187.27: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 103.16.102.112: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 194.116.96.46: set Speed to 10000 (10G) (now 1000).
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 VeriSign Global Registry Services has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 206.108.114.16 IPv6 2001:504:3c::16 Speed 1000 Mbps (1G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 71 |
| Nov 18, 2026 | 71 |
| Nov 17, 2026 | 71 |
| Nov 16, 2026 | 71 |
| Nov 15, 2026 | 71 |
| Nov 14, 2026 | 71 |
| Nov 13, 2026 | 71 |
| Nov 12, 2026 | 71 |
| Nov 11, 2026 | 71 |
| Nov 10, 2026 | 71 |
| Nov 9, 2026 | 71 |
| Nov 8, 2026 | 71 |
| Nov 7, 2026 | 71 |
| Nov 6, 2026 | 71 |
| Nov 5, 2026 | 71 |
| Nov 4, 2026 | 71 |
| Nov 3, 2026 | 71 |
| Nov 2, 2026 | 71 |
| Nov 1, 2026 | 71 |
| Oct 31, 2026 | 71 |
| Oct 30, 2026 | 71 |
| Oct 29, 2026 | 71 |
| Oct 28, 2026 | 71 |
| Oct 27, 2026 | 71 |
| Oct 26, 2026 | 71 |
| Oct 25, 2026 | 71 |
| Oct 24, 2026 | 71 |
| Oct 23, 2026 | 71 |
| Oct 22, 2026 | 71 |
| Oct 21, 2026 | 71 |
| Oct 20, 2026 | 71 |
| Oct 19, 2026 | 71 |
| Oct 18, 2026 | 71 |
| Oct 17, 2026 | 71 |
| Oct 16, 2026 | 71 |
| Oct 15, 2026 | 71 |
| Oct 14, 2026 | 71 |
| Oct 13, 2026 | 71 |
| Oct 12, 2026 | 71 |
| Oct 11, 2026 | 71 |
| Oct 10, 2026 | 71 |
| Oct 9, 2026 | 71 |
| Oct 8, 2026 | 71 |
| Oct 7, 2026 | 71 |
| Oct 6, 2026 | 71 |
| Oct 5, 2026 | 71 |
| Oct 4, 2026 | 71 |
| Oct 3, 2026 | 71 |
Map
Where VeriSign Global Registry Services's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| AAIX Klagenfurt, Austria | 1G | Both Speed differs | |
| AMS-IX Djibouti Djibouti, Djibouti | 1G | Both IPv6 differs | |
| angonix Luanda, Angola | 1G | PeeringDB | |
| BALT-IX Vilnius, Lithuania | 1G | Both | |
| BCIX Berlin, Germany | 1G | Both Speed differs | |
| BDIX Dhaka, Bangladesh | 1G | PeeringDB | |
| BKNIX (Thailand) Bangkok, Thailand | 1G | Both Speed differs | |
| CATNIX Barcelona, Spain | 1G | Both | |
| ChIX Chicago, United States | 1G | Both | |
| CIX Zagreb, Croatia | 1G | Both | |
| DE-CIX Mumbai Mumbai, India | 1G | Both | |
| DE-CIX Richmond Ashland, United States | 10G | Not in PeeringDB | |
| Digital Realty Atlanta Atlanta, United States | 1G | PeeringDB | |
| Equinix Tokyo Tokyo, Japan | 10G | PeeringDB | |
| FICIX 2 (Helsinki) Helsinki, Finland | 1G | Both | |
| FICIX 3 (Oulu) Oulu, Finland | 1G | PeeringDB | |
| France-IX Paris Paris, France | 10G | PeeringDB | |
| GetaFIX Manila Manila, Philippines | 1G | PeeringDB | |
| Giganet IXN Amsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 1G | PeeringDB | |
| GigaPIX - LAN 1 Lisbon, Portugal | 1G | Both | |
| GR-IX::Athens Athens, Greece | 1G | Both | |
| IIX Israel Petach Tikva, Israel | 1G | PeeringDB | |
| INEX LAN1 Dublin, Ireland | 1G | Both | |
| INEX LAN2 Dublin, Ireland | 1G | Both | |
| IX Australia Perth (WA-IX) Perth, Australia | 1G | Both Speed differs | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | Website list only | ||
| IX-Denver Denver, United States | 1G | Both Speed differs | |
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 1G | Both | |
| IXLeeds Leeds / Western Yorkshire, United Kingdom | 1G | Both | |
| IXPN Lagos Lagos, Nigeria | 1G | Both | |
| KCIX Kansas City, United States | 1G | Both | |
| KINX Seoul, South Korea | 1G | PeeringDB | |
| KIXP - Nairobi Nairobi, Kenya | 1G | Both | |
| LebIX Beirut, Lebanon | 1G | PeeringDB | |
| LINX Scotland Scotland, United Kingdom | 1G | Both | |
| LU-CIX Luxembourg, Luxembourg | 1G | Both | |
| MBIX Winnipeg, Manitoba, Canada | 1G | Both | |
| MegaIX Auckland Auckland, New Zealand | 1G | Both | |
| MegaIX Brisbane Brisbane, Australia | 1G | Both | |
| MegaIX Melbourne Melbourne, Australia | 1G | Both | |
| MegaIX Perth Perth, Australia | 1G | Both | |
| MegaIX Sydney Sydney, Australia | 1G | Both | |
| MIX-IT Milan, Italy | 1G | Both | |
| MSK-IX Moscow Moscow, Russia | 1G | Both | |
| NAPAfrica IX Cape Town Cape Town, South Africa | 1G | Both Speed differs | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 1G | Both Speed differs | |
| NetIX Sofia, Bulgaria | 1G | Both | |
| NIX.CZ Prague, Czechia | 1G | Both | |
| NIX.SK Bratislava, Slovakia | 1G | Both | |
| NIX1 Oslo, Norway | 1G | PeeringDB | |
| OpenIXP / NiCE Indonesia, Indonesia | 1G | PeeringDB | |
| PhillyIX Philadelphia, United States | 1G | Both | |
| PIT - Peru - Lima Lima, Peru | 1G | PeeringDB | |
| PIT Santiago - PIT Chile Santiago, Chile | 1G | PeeringDB | |
| RINEX Kigali, Rwanda | 1G | Both | |
| RIX Reykjavik, Iceland | 1G | Both Speed differs | |
| RTIX Tallinn, Estonia | 1G | PeeringDB | |
| SAIX Saudi Arabia Riyadh Riyadh, Saudi Arabia | 10G | Both | |
| SFMIX San Francisco, United States | 1G | Both Speed differs | |
| SGIX Singapore, Singapore | 1G | Both Speed differs | |
| SMILE-IXP Riga, Latvia | 1G | PeeringDB | |
| SOX Serbia Belgrade/Serbia, Serbia | 1G | PeeringDB | |
| STLIX Saint Louis, MO, United States | Website list only | ||
| SUPRnet Saint George, United States | 1G | Both | |
| SwissIX Zurich, Switzerland | 1G | Both | |
| TIX Tanzania - Dar es Salaam Dar es Salaam, Tanzania | 1G | Both | |
| TOP-IX Turin, Italy | 1G | Both Speed differs | |
| TPAIX Tampa, United States | 1G | PeeringDB only | |
| TWIX Taipei, Taiwan | 10G | PeeringDB | |
| VIX Vienna, Austria | 1G | Both | |
| YYCIX Calgary, Canada | 1G | Both |
VeriSign Global Registry Services lists no facilities in PeeringDB.
Recent changes Search them
- Nov 6, 2026 [PDB] AS26415 VeriSign Global Registry Services no longer in PeeringDB at CATNIX (still on its IX-F list)