subnet.im

108.165.4.0/23

TNGNET B.V.AS47690

At a glance

Addresses

512

/23 block

Visibility

99%

80 of 81 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 14th November 2011

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Oregon, US.

OriginVantage point · Oregon, US
One AS path to 108.165.4.0/23 as seen from Oregon, US, read outward from the origin: AS47690 → AS39521 → AS6206 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS47690TNGNET B.V.OriginAS39521TNGNET B.V.AS6206Netrouting B.V.AS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. 1AS47690TNGNET B.V.NLOrigin
    Peer of AS47690seen on 3,572 paths from 84 vantage points
  2. 2AS39521TNGNET B.V.NL
    Peer of AS39521seen on 2,833 paths from 81 vantage points
  3. 3AS6206Netrouting B.V.NL
    Peer of AS6206seen on 840 paths from 68 vantage points
  4. 4AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 987,848 paths from 1 vantage point
  5. 5AS20130Depaul UniversityUSVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. London, UK47690395216206291435280This path
  2. Sao Paulo47690395216206645335280This path
  3. Oregon, US47690395216206693920130Shown above
  4. Amsterdam476903952162066453250918298This path
  5. Singapore4769039521620629148966132337This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

99%

Seen by 80 of 81 full-feed vantage points

Globally propagated

Observed at 5 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
ARIN — North America
Country
United States
Allocated
14th November 2011
Allocation block
108.165.0.0/16
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 108.165.4.0/23
ROA prefixAuthorised originMax length
108.165.4.0/23AS47690/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 108.165.4.0/23
PrefixAddressesOriginVisibility
108.165.6.0/23512AS401152Ace Data Centers II, L.L.C.79/81

History

  1. AS4769022nd September 2026 — present
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Open 108.165.4.0/23 in the calculator/23 reference

Routing data derived from RouteViews MRT archives and public registry data.