subnet.im

217.20.220.0/23

At a glance

Addresses

512

/23 block

Visibility

99%

76 of 77 vantage points

RPKI

No ROA

Registry

RIPE NCCSY

Allocated 7th June 2010

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

  1. London, UK29386686667628529This path
  2. Sao Paulo293866866335635280This path
  3. Singapore293866866349123673This path
  4. Amsterdam2938668666762250918298This path
  5. Oregon, US29386686633561299855142013This path

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 propagated

Observed 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

Prefixes of the same length sharing a parent block with 217.20.220.0/23
PrefixAddressesOriginVisibility
217.20.222.0/23512AS29386Syrian Telecommunication Private Closed Joint Stock Company76/77

History

  1. AS2938622nd September 2026 — present
  2. AS292562nd November 2026 — 3rd November 2026
  3. AS292561st November 2026 — 1st November 2026
  4. AS2925612th August 2026 — 27th October 2026
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.