subnet.im

84.246.131.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCSE

Allocated 13th September 2004

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 84.246.131.0/24 as seen from Singapore, read outward from the origin: AS34236 → AS41943 → AS25146 → AS202780 → AS12552 → AS132337. Each hop is listed with its network name beneath the graph.AS34236Vaddo Media Infor…OriginAS41943Vaddo Media Infor…AS25146Advania Sverige ABAS202780Advania Sverige ABAS12552GlobalConnect (IP…AS132337Axclusive

Seen from Singapore

  1. Peer of AS34236seen on 480 paths from 80 vantage points
  2. Peer of AS41943seen on 702 paths from 142 vantage points
  3. Peer of AS25146seen on 800 paths from 80 vantage points
  4. Peer of AS202780seen on 2,368 paths from 80 vantage points
  5. Peer of AS12552seen on 1,819 paths from 2 vantage points
  6. 6AS132337AxclusiveSGVantage 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. Amsterdam34236419432514620278012552213151This path
  2. London, UK342364194325146202780125528529This path
  3. Singapore34236419432514620278012552132337Shown above
  4. Sao Paulo342364194325146202780125523356266213This path
  5. Oregon, US34236419432514620278012552693920130This 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

100%

Seen by 80 of 80 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Sweden
Allocated
13th September 2004
Allocation block
84.246.128.0/21
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 84.246.131.0/24
ROA prefixAuthorised originMax length
84.246.131.0/24AS34236/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 84.246.131.0/24
PrefixAddressesOriginVisibility
84.246.130.0/24256AS34236Vaddo Media Information IS AB80/80

History

  1. AS3423612th August 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 84.246.131.0/24 in the calculator/24 reference

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