31.77.178.0/23
ALLIANCE INTELLIGENT TECHNOLOGIES PTE. LTD.AS147003
Ace Data Centers II, L.L.C.AS401152
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/23 block
Visibility
1 of 78 vantage points
RPKI
Registry
USAllocated 25th November 2010
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 AS401152seen on 20,955 paths from 141 vantage points
- Peer of AS11798seen on 8,501 paths from 64 vantage points
- Peer of AS174seen on 186,356 paths from 23 vantage points
- Peer of AS6762seen on 33,218 paths from 1 vantage point
- Peer of AS1680seen on 35,557 paths from 1 vantage point
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
1%
Seen by 1 of 78 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
- 25th November 2010
- Allocation block
- 31.76.0.0/15
- 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.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 31.77.178.0/24 | 256 | AS219147Moskalev Georgiy | 75/78 |
| 31.77.179.0/24 | 256 | AS219147Moskalev Georgiy | 78/78 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 31.77.176.0/23 | 512 | AS4766Korea Telecom | 78/78 |
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 31.77.178.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.