AS17616 — BAROFN-AS-KR-KR - barofn
🇰🇷 South Korea · APNIC region · approx. 37.39, 126.94
BAROFN-AS-KR-KR - barofn (AS17616) in South Korea has 2 direct BGP neighbours, ranked #31365 of 88104 by observed links.
Network intelligence
Neighbourhood
What's directly and indirectly (up to two hops) connected to AS17616 — the same force-directed layout as the main Topology view, computed fresh on every page load (reload for a different arrangement), with AS17616 itself always centred. Drag to pan, scroll/pinch to zoom, click a dot to jump to that AS's own page. Explore the full interactive map →
Announced prefixes
RPKI route-origin validity badge per prefix, from this instance's self-hosted Routinator (see Credits). The full, de-duplicated set seen across every BGP collector this snapshot imports — usually more than the “IPv4/IPv6 prefixes” counts above, which only reflect a single collector's own routing table.
- 61.255.135.0/25 RPKI Not Found
- 103.139.214.0/24 RPKI Not Found
- 103.139.214.0/25 RPKI Not Found
- 103.139.214.128/25 RPKI Not Found
- 103.139.215.0/24 RPKI Not Found
- 103.139.215.0/25 RPKI Not Found
- 103.139.215.128/25 RPKI Not Found
- 115.88.40.0/26 RPKI Not Found
- 115.88.40.0/27 RPKI Not Found
- 115.88.40.32/27 RPKI Not Found
- 115.88.40.64/26 RPKI Not Found
- 115.88.40.128/26 RPKI Not Found
- 115.88.40.128/27 RPKI Not Found
- 115.88.40.160/27 RPKI Not Found
- 115.88.40.192/26 RPKI Not Found
- 211.250.156.0/26 RPKI Not Found
- 211.250.156.0/27 RPKI Not Found
- 211.250.156.32/27 RPKI Not Found
- 211.250.156.128/26 RPKI Not Found
- 211.250.156.128/27 RPKI Not Found
No loaded prefix matches that filter. Try loading more below, or narrow/widen the filter text.
...and 5 more.
Upstream providers (2)
Networks that this AS is a customer of (inferred from public BGP data by BGPKIT's as2rel dataset, a heuristic, not ground truth).
Geographic footprint
Geolocated (estimated) country of every prefix AS17616 announces, via IP geolocation against DB-IP City Lite — not AS17616's RIR registration country (see the stats above), and not necessarily where its infrastructure physically sits.