Observed topology
AS49304 SAKURA-AS
Unclassified APNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS49304: 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 |
|---|---|---|---|---|
| AS9516 | SAKURA LINK LIMITED | Unclassified | IPv4 IPv6 | 3,029 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 869 |
| AS17676 | SoftBank Corp. | Mobile | IPv4 | 529 |
| AS202069 | Sakura Communications Limited | Unclassified | IPv4 | 446 |
| AS21859 | Zenlayer Inc | Hosting | IPv4 | 130 |
| AS2516 | KDDI CORPORATION | Mobile | IPv4 | 117 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 113 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 73 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 18 |
| AS32346 | SAKURA LTD. | Unclassified | IPv4 | 18 |
Transit
Downstream networks
Networks for which AS49304 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS209554 | ISIF OU | Residential | IPv4 IPv6 | 1,028 |
| AS18464 | ALVIDI TECHNOLOGY Inc | Hosting | IPv4 IPv6 | 821 |
| AS63150 | BAGE CLOUD LLC | Hosting | IPv4 IPv6 | 796 |
| AS32135 | SAKURA LTD. | Unclassified | IPv4 | 792 |
| AS205548 | ZOUTER LIMITED | Unclassified | IPv4 IPv6 | 730 |
| AS399870 | BYNARIUM LLC | Unclassified | IPv4 IPv6 | 631 |
| AS8143 | Neburst LLC | Unclassified | IPv4 IPv6 | 565 |
| AS396856 | Sharon Networks, LLC | Unclassified | IPv4 | 362 |
| AS36002 | GoMami Networks | Unclassified | IPv4 | 350 |
| AS202069 | Sakura Communications Limited | Unclassified | IPv4 | 312 |
Adjacency
Adjacent networks
Every AS seen directly next to AS49304 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9516 | SAKURA LINK LIMITED | Unclassified | IPv4 IPv6 | 9,974 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,819 |
| AS4743 | ISIF LIMITED | Unclassified | IPv4 IPv6 | 1,938 |
| AS209554 | ISIF OU | Residential | IPv4 IPv6 | 1,029 |
| AS399870 | BYNARIUM LLC | Unclassified | IPv4 IPv6 | 837 |
| AS202069 | Sakura Communications Limited | Unclassified | IPv4 | 826 |
| AS18464 | ALVIDI TECHNOLOGY Inc | Hosting | IPv4 IPv6 | 821 |
| AS63150 | BAGE CLOUD LLC | Hosting | IPv4 IPv6 | 796 |
| AS32135 | SAKURA LTD. | Unclassified | IPv4 | 792 |
| AS205548 | ZOUTER LIMITED | Unclassified | IPv4 IPv6 | 730 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-27 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.06M 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.