130.137.90.0/24
At a glance
Addresses
/24 block
Visibility
56 of 78 vantage points
RPKI
Registry
USAllocated 14th February 2018
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 AS16509seen on 303,702 paths from 139 vantage points
- Peer of AS1299seen on 383,819 paths from 2 vantage points
SE
AEOne 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
- Sao Paulo1650935280This path
- London, UK1650912998529Shown above
- Amsterdam1650990022063757768This path
- Oregon, US165093257855142013This 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
72%
Seen by 56 of 78 full-feed vantage points
Partially 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
- ARIN — North America
- Country
- United States
- Allocated
- 14th February 2018
- Allocation block
- 130.137.0.0/16
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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
No prefix of the same length in the same parent block is announced.
History
- AS1650913th November 2026 — present
- AS1650912th November 2026 — 12th November 2026
- AS1650910th November 2026 — 10th November 2026
- AS1650910th November 2026 — 10th November 2026
- AS165098th November 2026 — 8th November 2026
- AS165097th November 2026 — 7th November 2026
- AS165095th November 2026 — 5th November 2026
- AS165092nd November 2026 — 2nd November 2026
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 130.137.90.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.