178.94.116.0/24
At a glance
Addresses
/24 block
Visibility
21 of 76 vantage points
RPKI
Registry
UAAllocated 15th December 2009
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS219447seen on 1,617 paths from 76 vantage points
- Peer of AS62610seen on 67,595 paths from 139 vantage points
- Peer of AS21859seen on 13,014 paths from 128 vantage points
- Peer of AS3257seen on 211,917 paths from 31 vantage points
- Peer of AS3491seen on 86,654 paths from 2 vantage points
HK
US
KHOne 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.
Route visibility
28%
Seen by 21 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
- Ukraine
- Allocated
- 15th December 2009
- Allocation block
- 178.92.0.0/14
- 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
No prefix of the same length in the same parent block is announced.
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 178.94.116.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.