Observed topology
AS133210 ENTECHNOLOGIES-AS-AP EN Technologies Pte Ltd
Transit
Upstream networks
Networks observed carrying traffic for AS133210: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS56308 | TELEKOMUNIKASI INDONESIA INTERNATIONAL, PTE.LTD | Unclassified | IPv4 IPv6 | 910 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 171 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 21 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 21 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 21 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 | 17 |
| AS61292 | Blix Group AS | Unclassified | IPv6 | 4 |
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you.
Transit
Downstream networks
Networks for which AS133210 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS211407 | PT Perwira Media Solusi | Hosting | IPv4 | 603 |
| AS58885 | IQON GLOBAL PTE LTD | Hosting | IPv4 | 480 |
| AS153454 | BYIO SINGAPORE PTE. LTD. | Unclassified | IPv4 IPv6 | 217 |
| AS154373 | Singapore Data Cloud Pte Ltd | Unclassified | IPv4 IPv6 | 214 |
| AS135134 | Soon Keat Neo | Unclassified | IPv4 IPv6 | 175 |
| AS149448 | Singapore Data Cloud PTE. LTD | Unclassified | IPv4 | 120 |
| AS139989 | CV Atha Media Prima | Hosting | IPv4 IPv6 | 92 |
| AS153164 | ASIA CLOUD HOSTING | Unclassified | IPv4 | 60 |
| AS141634 | PT Satu Sistem Integrasi | Unclassified | IPv4 | 60 |
| AS150158 | PHSS CAM INDO CO,. LTD. | Unclassified | IPv4 | 48 |
| AS140405 | PT. Cybertechtonic Pratama | Unclassified | IPv4 IPv6 | 44 |
| AS47311 | PT Atharva Telematika Persada | Unclassified | IPv6 | 35 |
Adjacency
Adjacent networks
Every AS seen directly next to AS133210 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS56308 | TELEKOMUNIKASI INDONESIA INTERNATIONAL, PTE.LTD | Unclassified | IPv4 IPv6 | 2,601 |
| AS211407 | PT Perwira Media Solusi | Hosting | IPv4 | 603 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 521 |
| AS58885 | IQON GLOBAL PTE LTD | Hosting | IPv4 | 480 |
| AS153454 | BYIO SINGAPORE PTE. LTD. | Unclassified | IPv4 IPv6 | 217 |
| AS154373 | Singapore Data Cloud Pte Ltd | Unclassified | IPv4 IPv6 | 214 |
| AS135134 | Soon Keat Neo | Unclassified | IPv4 IPv6 | 175 |
| AS47311 | PT Atharva Telematika Persada | Unclassified | IPv4 IPv6 | 128 |
| AS149448 | Singapore Data Cloud PTE. LTD | Unclassified | IPv4 | 120 |
| AS139989 | CV Atha Media Prima | Hosting | IPv4 IPv6 | 100 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 72 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 71 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 61 |
| AS141634 | PT Satu Sistem Integrasi | Unclassified | IPv4 | 60 |
| AS153164 | ASIA CLOUD HOSTING | Unclassified | IPv4 | 60 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 | 51 |
| AS150158 | PHSS CAM INDO CO,. LTD. | Unclassified | IPv4 | 48 |
| AS140405 | PT. Cybertechtonic Pratama | Unclassified | IPv4 IPv6 | 45 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 14 |
| AS61292 | Blix Group AS | Unclassified | IPv6 | 14 |
| AS9930 | TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malaysia | Unclassified | IPv4 | 6 |
| AS8966 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Mobile | IPv4 IPv6 | 2 |
| AS7575 | Australian Academic and Research Network (AARNet) | Education | IPv4 | 1 |
| AS35280 | F5 Networks SARL | Hosting | IPv6 | 1 |
Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Interconnection
Exchange presence
Internet exchanges where Packet Clearing House has a port recorded for AS133210, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 2 exchanges across 1 country and 1 region.
| Exchange | Location | Their address | Member ports |
|---|---|---|---|
| Equinix Internet Exchange Singapore | Singapore, Singapore | 27.111.230.35 | 490 |
| Singapore Internet Exchange | Singapore, Singapore | 103.16.102.230 | 273 |
Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.
Provenance
Where this comes from
Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.
Exchange presence comes from a separate dataset: the directory collected 2026-08-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 recorded member ports, licensed CC BY-NC-SA 3.0.
PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.