156.154.101.0/24
At a glance
Addresses
/24 block
Visibility
56 of 81 vantage points
RPKI
Registry
USAllocated 18th December 2003
AS paths to this prefix
One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.
- London, UK19905291435280This path
- Sao Paulo19905645335280This path
- Singapore1200816552132337This path
- Amsterdam199056453250918298This path
- Oregon, US1990532572335220130This 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
69%
Seen by 56 of 81 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
- 18th December 2003
- Allocation block
- 156.154.96.0/20
- 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 |
|---|---|---|
| 156.154.101.0/24 | AS12008 | /24 |
| 156.154.101.0/24 | AS19905 | /24 |
| 156.154.101.0/24 | AS397213 | /24 |
| 156.154.101.0/24 | AS397214 | /24 |
| 156.154.101.0/24 | AS397215 | /24 |
| 156.154.101.0/24 | AS397216 | /24 |
| 156.154.101.0/24 | AS397217 | /24 |
| 156.154.101.0/24 | AS397218 | /24 |
| 156.154.101.0/24 | AS397219 | /24 |
| 156.154.101.0/24 | AS397220 | /24 |
| 156.154.101.0/24 | AS397221 | /24 |
| 156.154.101.0/24 | AS397222 | /24 |
| 156.154.101.0/24 | AS397223 | /24 |
| 156.154.101.0/24 | AS397224 | /24 |
| 156.154.101.0/24 | AS397225 | /24 |
| 156.154.101.0/24 | AS397226 | /24 |
| 156.154.101.0/24 | AS397227 | /24 |
| 156.154.101.0/24 | AS397228 | /24 |
| 156.154.101.0/24 | AS397229 | /24 |
| 156.154.101.0/24 | AS397230 | /24 |
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 |
|---|---|---|---|
| 156.154.100.0/24 | 256 | AS12008Vercara (f.k.a Neustar) | 23/81 |
| 156.154.100.0/24 | 256 | AS19905Arbor Cloud | 56/81 |
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 156.154.101.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.