134.214.0.0/16
At a glance
Addresses
/16 block
Visibility
77 of 80 vantage points
RPKI
Registry
FRAllocated 25th July 1989
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Oregon, US.
Seen from Oregon, US
- Peer of AS2060seen on 77 paths from 77 vantage points
- Peer of AS1945seen on 442 paths from 80 vantage points
- Peer of AS2200seen on 433 paths from 12 vantage points
- Peer of AS6939seen on 975,334 paths from 1 vantage point
EU
USOne 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
- Singapore206019452200132337This path
- Oregon, US206019452200693920130Shown above
- London, UK2060194522002132026038529This path
- Sao Paulo2060194522001743356266213This path
- Amsterdam20601945220021320260334549213151This 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
96%
Seen by 77 of 80 full-feed vantage points
Globally propagatedObserved 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
- France
- Allocated
- 25th July 1989
- Allocation block
- 134.214.0.0/16
- Status
- assigned
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 134.215.0.0/16 | 65.5k | AS4181TDS TELECOM | 80/80 |
History
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 134.214.0.0/16 in the calculator/16 reference
Routing data derived from RouteViews MRT archives and public registry data.