177.1.198.0/24
Ace Data Centers II, L.L.C.AS401152
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
20 of 76 vantage points
RPKI
Registry
USAllocated 13th 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 AS199180seen on 1 path from 1 vantage point
- Peer of AS50340seen on 7,407 paths from 85 vantage points
- Peer of AS20485seen on 18,196 paths from 35 vantage points
- Peer of AS6762seen on 33,086 paths from 1 vantage point
- Peer of AS1680seen on 35,424 paths from 1 vantage point
AM
RU
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
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
26%
Seen by 20 of 76 full-feed vantage points
Seen by few vantage pointsObserved at 1 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 States
- Allocated
- 13th March 2025
- Allocation block
- 177.1.192.0/20
- 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.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 177.1.198.0/24 | AS199180 | /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 |
|---|---|---|---|
| 177.1.199.0/24 | 256 | AS49505JSC Selectel | 9/76 |
| 177.1.199.0/24 | 256 | AS401152Ace Data Centers II, L.L.C. | 66/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 177.1.198.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.