193.108.57.0/24
At a glance
Addresses
/24 block
Visibility
55 of 76 vantage points
RPKI
Registry
UAAllocated 24th April 2001
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Oregon, US.
Seen from Oregon, US
- Adjacentseen on 55 paths from 55 vantage points
- Peer of AS214639seen on 1,948 paths from 137 vantage points
- Peer of AS49581seen on 43,883 paths from 126 vantage points
- Peer of AS44592seen on 6,648 paths from 89 vantage points
- Peer of AS6424seen on 40,125 paths from 139 vantage points
- Peer of AS1299seen on 324,212 paths from 1 vantage point
- Peer of AS8551seen on 1,077,043 paths from 1 vantage point
EU
EE
DE
NL
PT
SE
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
- Amsterdam218135214639495818298This path
- London, UK21813521463949581445928529This path
- Sao Paulo21813521463949581645335280This path
- Oregon, US218135214639495814459264241299855142013Shown 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
72%
Seen by 55 of 76 full-feed vantage points
Partially propagatedObserved at 4 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
- 24th April 2001
- Allocation block
- 193.108.56.0/22
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 193.108.57.0/24 | AS218135 | /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 |
|---|---|---|---|
| 193.108.56.0/24 | 256 | AS210699WEDEPLOY SAS | 76/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 193.108.57.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.