subnet.im

46.243.168.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCNL

Allocated 28th December 2010

AS paths to this prefix

All paths

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

OriginVantage point · Amsterdam
One AS path to 46.243.168.0/24 as seen from Amsterdam, read outward from the origin: AS202795 → AS35000 → AS12389 → AS6939 → AS213151. Each hop is listed with its network name beneath the graph.AS202795"Trans-Missia" LLCOriginAS35000JSC "Severen-Tele…AS12389Rostelecom PJSCAS6939Hurricane Electri…AS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS202795seen on 79 paths from 79 vantage points
  2. Peer of AS35000seen on 4,189 paths from 80 vantage points
  3. Peer of AS12389seen on 526,463 paths from 116 vantage points
  4. Peer of AS6939seen on 309,709 paths from 2 vantage points
  5. 5AS213151Christian ElsenDEVantage 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, UK20279535000123898529This path
  2. Amsterdam20279535000123896939213151Shown above
  3. Singapore20279535000123894766132337This path
  4. Oregon, US2027953500012389693920130This path
  5. Sao Paulo202795350001238934913356266213This 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 79 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
Netherlands
Allocated
28th December 2010
Allocation block
46.243.168.0/22
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 46.243.168.0/24
ROA prefixAuthorised originMax length
46.243.168.0/24AS202795/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 46.243.168.0/24
PrefixAddressesOriginVisibility
46.243.169.0/24256AS203563Vostok LLC80/80

History

  1. AS1012th August 2026 present
  2. AS20279512th 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 46.243.168.0/24 in the calculator/24 reference

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