130.12.180.0/24
At a glance
Addresses
/24 block
Visibility
5 of 76 vantage points
RPKI
Registry
USAllocated 8th October 2025
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 AS202412seen on 4 paths from 1 vantage point
- Peer of AS51396seen on 3,247 paths from 137 vantage points
- Peer of AS49581seen on 40,588 paths from 125 vantage points
- Peer of AS44592seen on 6,423 paths from 67 vantage points
- Peer of AS64289seen on 309 paths from 4 vantage points
- Peer of AS46427seen on 52 paths from 1 vantage point
- Peer of AS6762seen on 33,047 paths from 1 vantage point
- Peer of AS1680seen on 35,380 paths from 1 vantage point
SC
DE
NL
IT
IL
PSOne 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
- Singapore6461584533862323673This path
- Oregon, US202412513964958144592642894642767621680→ ⋯Shown above
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
7%
Seen by 5 of 76 full-feed vantage points
Seen by few vantage pointsObserved at 2 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
- 8th October 2025
- Allocation block
- 130.12.180.0/22
- Status
- allocated
- Origin validation
- Invalid
A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.
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 |
|---|---|---|---|
| 130.12.181.0/24 | 256 | AS197769VPS Dedicated LLC | 76/76 |
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 130.12.180.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.