Chief
AS17408 · Abovenet Taiwan
Chief Telecom Inc.
Tools: Where can I peer with Chief? · Where should Chief peer next? · Compare Chief with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
One thing to fix in Chief's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 18:41 UTC.
Make the changes on Chief'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 Chief's PeeringDB record. Add one entry per connection with these values.
-
IPv4 80.81.193.9 IPv6 2001:7f8::4400:0:1 Speed 10000 Mbps (10G) RS peer Yes
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 10 |
| Nov 18, 2026 | 10 |
| Nov 17, 2026 | 10 |
| Nov 16, 2026 | 10 |
| Nov 15, 2026 | 10 |
| Nov 14, 2026 | 10 |
| Nov 13, 2026 | 10 |
| Nov 12, 2026 | 10 |
| Nov 11, 2026 | 10 |
| Nov 10, 2026 | 10 |
| Nov 9, 2026 | 10 |
| Nov 8, 2026 | 10 |
| Nov 7, 2026 | 10 |
| Nov 6, 2026 | 10 |
| Nov 5, 2026 | 10 |
| Nov 4, 2026 | 10 |
| Nov 3, 2026 | 10 |
| Nov 2, 2026 | 10 |
| Nov 1, 2026 | 10 |
| Oct 31, 2026 | 10 |
| Oct 30, 2026 | 10 |
| Oct 29, 2026 | 10 |
| Oct 28, 2026 | 10 |
| Oct 27, 2026 | 10 |
| Oct 26, 2026 | 10 |
| Oct 25, 2026 | 10 |
| Oct 24, 2026 | 10 |
| Oct 23, 2026 | 10 |
| Oct 22, 2026 | 10 |
| Oct 21, 2026 | 10 |
| Oct 20, 2026 | 10 |
| Oct 19, 2026 | 10 |
| Oct 18, 2026 | 10 |
| Oct 17, 2026 | 10 |
| Oct 16, 2026 | 10 |
| Oct 15, 2026 | 10 |
| Oct 14, 2026 | 10 |
| Oct 13, 2026 | 10 |
| Oct 12, 2026 | 10 |
| Oct 11, 2026 | 10 |
| Oct 10, 2026 | 10 |
| Oct 9, 2026 | 10 |
| Oct 8, 2026 | 10 |
| Oct 7, 2026 | 10 |
| Oct 6, 2026 | 10 |
| Oct 5, 2026 | 10 |
| Oct 4, 2026 | 10 |
| Oct 3, 2026 | 10 |
Map
Where Chief'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.
| AMS-IX Hong Kong Hong Kong, Hong Kong | 1G | Both | |
| AMS-IX Singapore Singapore, Singapore | 1G | Both | |
| DE-CIX Frankfurt Frankfurt, Germany | 10G | Not in PeeringDB | |
| Equinix Hong Kong Hong Kong, Hong Kong | 10G | PeeringDB | |
| FOX Tainan, Taiwan | 10G | PeeringDB | |
| JPIX TOKYO Tokyo, Japan | 10G | Both | |
| SGIX Singapore, Singapore | 10G | Both | |
| STUIX Taipei City, Taiwan | 10G | Both | |
| TPIX-TW Taipei/Taiwan, Taiwan | 100G + 2 × 80G | PeeringDB | |
| TWIX Taipei, Taiwan | 10G | PeeringDB |
These exchanges have a switch in a facility where Chief lists itself in PeeringDB, but don't have Chief as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.
| NetIXSofia, Bulgaria | 204 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (1)
The buildings Chief lists in PeeringDB, and how many of the exchanges in each it's on.
| Chief LY Building TaipeiTaipei | 3 of 5 |
Recent changes Search them
- Oct 7, 2026 [PDB] AS17408 Chief no longer in PeeringDB at DE-CIX Frankfurt (still on its IX-F list and on its website's members list)