177.177.74.0/24
At a glance
Addresses
/24 block
Visibility
79 of 81 vantage points
RPKI
Registry
AEAllocated 6th March 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 AS402857seen on 3,519 paths from 80 vantage points
- Peer of AS29752seen on 13,511 paths from 143 vantage points
- Peer of AS3257seen on 60,106 paths from 1 vantage point
- Peer of AS23352seen on 105,806 paths from 1 vantage point
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
- London, UK402857297522185935280This path
- Singapore4028572975221859132337This path
- Sao Paulo402857297523257645335280This path
- Oregon, US4028572975232572335220130Shown above
- Amsterdam402857297522185968305786682838298This 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
98%
Seen by 79 of 81 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
- United Arab Emirates
- Allocated
- 6th March 2025
- Allocation block
- 177.177.64.0/19
- Status
- allocated
- 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 |
|---|---|---|---|
| 177.177.75.0/24 | 256 | AS402857Highland Trek Outdoor Camping Supplies LLC | 77/81 |
History
- AS40285726th September 2026 — present
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 177.177.74.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.