2a14:1ec1:1700::/40
At a glance
Subnets
/40 block
Visibility
62 of 63 vantage points
RPKI
Registry
NLAllocated 13th March 2024
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS219523seen on 124 paths from 62 vantage points
- Peer of AS207252seen on 3,483 paths from 130 vantage points
- Peer of AS50629seen on 7,883 paths from 64 vantage points
- Peer of AS2914seen on 438,988 paths from 6 vantage points
DE
US
FROne 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
- Amsterdam219523207252506298298This path
- Singapore21952320725250629132337This path
- London, UK21952320725250629291435280Shown above
- Sao Paulo21952320725250629291435280This 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 62 of 63 full-feed vantage points
Globally propagatedObserved 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
- 13th March 2024
- Allocation block
- 2a14:1ec0::/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
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 2a14:1ec1:1700::/40 | AS219523 | /40 |
| 2a14:1ec1:1000::/36 | AS211066 | /48 |
| 2a14:1ec1:1000::/36 | AS215136 | /48 |
| 2a14:1ec1::/32 | AS207252 | /32 |
| 2a14:1ec1::/32 | AS48700 | /48 |
| 2a14:1ec0::/31 | AS14618 | /48 |
| 2a14:1ec0::/31 | AS16509 | /48 |
| 2a14:1ec0::/31 | AS48700 | /48 |
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a14:1ec1::/32 | 4.3B × /64 | AS207252Felix Gassan | 62/63 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a14:1ec1:1600::/40 | 16.8M × /64 | AS219523Markus Tyebo trading as Tyebo Infrastructure & Consulting | 62/63 |
History
- AS21952312th 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.