193.8.185.0/24
At a glance
Addresses
/24 block
Visibility
80 of 81 vantage points
RPKI
Registry
BGAllocated 24th April 2018
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 AS215691seen on 1,277 paths from 80 vantage points
- Peer of AS174seen on 241,777 paths from 46 vantage points
- Peer of AS3257seen on 59,694 paths from 1 vantage point
- Peer of AS23352seen on 105,410 paths from 1 vantage point
ES
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
- Singapore215691174132337This path
- London, UK215691174129935280This path
- Sao Paulo215691174645335280This path
- Amsterdam2156911746762250918298This path
- Oregon, US21569117432572335220130Shown above
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
99%
Seen by 80 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
- Bulgaria
- Allocated
- 24th April 2018
- Allocation block
- 193.8.184.0/22
- 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 |
|---|---|---|---|
| 193.8.184.0/24 | 256 | AS41745Baykov Ilya Sergeevich | 81/81 |
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 193.8.185.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.