subnet.im

82.41.3.0/24

NETGRID HOST LTDAS202051

Matteo Fruhwald trading as PipeHost e.U.AS64457

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

96%

77 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCGB

Allocated 31st January 2003

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 82.41.3.0/24 as seen from Oregon, US, read outward from the origin: AS202051 → AS59729 → AS9002 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS202051NETGRID HOST LTDOriginAS59729ROUTE 95 LLCAS9002RETN LimitedAS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. 1AS202051NETGRID HOST LTDGBOrigin
    Peer of AS202051seen on 156 paths from 79 vantage points
  2. 2AS59729ROUTE 95 LLCUS
    Peer of AS59729seen on 919 paths from 85 vantage points
  3. 3AS9002RETN LimitedGB
    Peer of AS9002seen on 12,631 paths from 36 vantage points
  4. 4AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 975,334 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, UK2020515972990028529This path
  2. Singapore2020515972950263132337This path
  3. Amsterdam2020515972917434549213151This path
  4. Sao Paulo2020515972990023356266213This path
  5. Oregon, US202051597299002693920130Shown above

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

96%

Seen by 77 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
United Kingdom
Allocated
31st January 2003
Allocation block
82.40.0.0/15
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 82.41.3.0/24
ROA prefixAuthorised originMax length
82.41.3.0/24AS202051/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 82.41.3.0/24
PrefixAddressesOriginVisibility
82.41.2.0/24256AS211895Serverius Holding B.V.79/80

History

  1. AS20205112th August 2026 — present
  2. AS6445712th 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 82.41.3.0/24 in the calculator/24 reference

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