217.20.220.0/23
At a glance
Addresses
/23 block
Visibility
76 of 77 vantage points
RPKI
Registry
SYAllocated 7th June 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 AS29386seen on 25,363 paths from 139 vantage points
- Peer of AS6866seen on 7,032 paths from 78 vantage points
- Peer of AS3356seen on 584,864 paths from 65 vantage points
- Peer of AS1299seen on 321,401 paths from 1 vantage point
- Peer of AS8551seen on 1,077,432 paths from 1 vantage point
CY
US
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
- London, UK29386686667628529This path
- Sao Paulo293866866335635280This path
- Singapore293866866349123673This path
- Amsterdam2938668666762250918298This path
- Oregon, US29386686633561299855142013Shown 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 76 of 77 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
- Syria
- Allocated
- 7th June 2010
- Allocation block
- 217.20.208.0/20
- 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.
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 |
|---|---|---|---|
| 217.20.222.0/23 | 512 | AS29386Syrian Telecommunication Private Closed Joint Stock Company | 76/77 |
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 217.20.220.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.