subnet.im

2a07:b700::/29

E-Zorg B.V.AS57626

At a glance

Subnets

34,359,738,368 × /64

/29 block

Visibility

98%

61 of 62 vantage points

RPKI

Valid

Registry

RIPE NCCNL

Allocated 15th July 2016

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 2a07:b700::/29 as seen from Amsterdam, read outward from the origin: AS57626 → AS20562 → AS213151. Each hop is listed with its network name beneath the graph.AS57626E-Zorg B.V.OriginAS20562Open Peering (Bro…AS213151Christian Elsen

Seen from Amsterdam

  1. 1AS57626E-Zorg B.V.NLOrigin
    Peer of AS57626seen on 303 paths from 67 vantage points
  2. 2AS20562Open Peering (Broadband Hosting B.V.)NL
    Peer of AS20562seen on 2,358 paths from 2 vantage points
  3. 3AS213151Christian 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. Singapore57626132337This path
  2. Amsterdam5762620562213151Shown above
  3. London, UK576262056251907This path
  4. Sao Paulo57626693932590This 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

98%

Seen by 61 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
Netherlands
Allocated
15th July 2016
Allocation block
2a07:b700::/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 2a07:b700::/29
ROA prefixAuthorised originMax length
2a07:b700::/29AS57626/30

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2a07:b700::/29: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2a07:b700::/29AS57626This prefix2a07:b700::/30AS576262a07:b704::/30AS57626

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Announcements contained within 2a07:b700::/29
PrefixAddressesOriginVisibility
2a07:b700::/3017.2B × /64AS57626E-Zorg B.V.61/62
2a07:b704::/3017.2B × /64AS57626E-Zorg B.V.61/62

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

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