subnet.im

2a0e:e704:44::/48

ALAIN BITSCHINEAS212971

At a glance

Subnets

65,536 × /64

/48 block

Visibility

100%

62 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCFR

Allocated 3rd May 2019

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 2a0e:e704:44::/48 as seen from London, UK, read outward from the origin: AS212971 → AS2027 → AS35625 → AS51907. Each hop is listed with its network name beneath the graph.AS212971ALAIN BITSCHINEOriginAS2027MilkyWanAS35625Eurofiber France …AS51907Kanton Zug

Seen from London, UK

  1. 1AS212971ALAIN BITSCHINEFROrigin
    Peer of AS212971seen on 56 paths from 56 vantage points
  2. 2AS2027MilkyWanFR
    Peer of AS2027seen on 205 paths from 17 vantage points
  3. 3AS35625Eurofiber France SASFR
    Peer of AS35625seen on 348 paths from 2 vantage points
  4. 4AS51907Kanton ZugCHVantage 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. Amsterdam212971202735625213151This path
  2. London, UK21297120273562551907Shown above
  3. Sao Paulo21297120273528032590This path
  4. Singapore212971202749434132337This 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 62 of 62 full-feed vantage points

Globally propagated

Observed at 4 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
France
Allocated
3rd May 2019
Allocation block
2a0e:e700::/29
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 2a0e:e704:44::/48
ROA prefixAuthorised originMax length
2a0e:e704:44::/48AS212971/48

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 2a0e:e704:44::/48
PrefixAddressesOriginVisibility
2a0e:e704:45::/4865.5k × /64AS212970Teddy CHEREAU62/62

History

  1. AS21297112th 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.

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