207.174.22.0/24
At a glance
Addresses
/24 block
Visibility
55 of 76 vantage points
RPKI
Registry
USAllocated 6th April 2023
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS31916seen on 193 paths from 138 vantage points
- Peer of AS13649seen on 6,510 paths from 44 vantage points
- Peer of AS7922seen on 69,214 paths from 56 vantage points
- Peer of AS6453seen on 653,191 paths from 6 vantage points
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
- Singapore136493257335623673This path
- Amsterdam31916136493257250918298This path
- London, UK3191613649325712998529This path
- Sao Paulo31916136497922645335280Shown above
- Oregon, US319161364932571299855142013This 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 55 of 76 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
- 6th April 2023
- Allocation block
- 207.174.22.0/24
- 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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 207.174.23.0/24 | 256 | AS26001BLUIP INC | 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 207.174.22.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.