Observed topology
AS137366 IFORTE-NAP-AS-ID PT iForte Solusi Infotek
Unclassified APNIC NSP
Transit
Upstream networks
Networks observed carrying traffic for AS137366: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 143 |
| AS7473 | Singapore Telecommunications Ltd | Unclassified | IPv4 | 129 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 104 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 47 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 40 |
| AS137367 | PT iForte Solusi Infotek | Residential | IPv4 | 9 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS137366 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS17995 | PT iForte Global Internet | Unclassified | IPv4 IPv6 | 36,790 |
| AS23951 | PT JEMBATAN CITRA NUSANTARA | Residential | IPv4 IPv6 | 4,522 |
| AS45287 | Varnion Technology Semesta, PT | Residential | IPv4 IPv6 | 2,153 |
| AS55699 | PT. Cemerlang Multimedia | Residential | IPv4 IPv6 | 1,353 |
| AS38778 | PT. Dutakom Wibawa Putra | Hosting | IPv4 IPv6 | 934 |
| AS45710 | Yudhawira Khatulistiwa, PT | Unclassified | IPv4 | 846 |
| AS38769 | PT. Bit Technology Nusantara | Unclassified | IPv4 | 743 |
| AS136873 | MEGADATA-ISP | Residential | IPv4 | 723 |
| AS9785 | PT Berca Hardayaperkasa | Unclassified | IPv4 | 700 |
| AS138855 | PT iForte Solusi Infotek | Unclassified | IPv4 | 693 |
Adjacency
Adjacent networks
Every AS seen directly next to AS137366 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 53,463 |
| AS17995 | PT iForte Global Internet | Unclassified | IPv4 IPv6 | 46,271 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 8,101 |
| AS23951 | PT JEMBATAN CITRA NUSANTARA | Residential | IPv4 IPv6 | 5,509 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 5,390 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,115 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 2,966 |
| AS45287 | Varnion Technology Semesta, PT | Residential | IPv4 IPv6 | 2,185 |
| AS137367 | PT iForte Solusi Infotek | Residential | IPv4 IPv6 | 1,621 |
| AS7473 | Singapore Telecommunications Ltd | Unclassified | IPv4 IPv6 | 1,443 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
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. 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.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.