SUBNET.IM

5.223.0.0/17

Hetzner Cloud - SingaporeAS215859

At a glance

Addresses

32,768

/17 block

Visibility

30%

24 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCDE

Allocated 4th September 2012

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Oregon, US.

OriginVantage point · Oregon, US
One AS path to 5.223.0.0/17 as seen from Oregon, US, read outward from the origin: AS215859 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS215859Hetzner Cloud - S…OriginAS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. 1AS215859Hetzner Cloud - SingaporeDEOrigin
    Peer of AS215859seen on 410 paths from 5 vantage points
  2. 2AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 975,334 paths from 1 vantage point
  3. 3AS20130Depaul UniversityUSVantage point

One 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

  1. Singapore215859132337This path
  2. Oregon, US215859693920130Shown above
  3. Amsterdam21585969395829941051213151This 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

30%

Seen by 24 of 80 full-feed vantage points

Seen by few vantage points

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
Germany
Allocated
4th September 2012
Allocation block
5.223.0.0/17
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 5.223.0.0/17
ROA prefixAuthorised originMax length
5.223.0.0/16AS215859/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 5.223.0.0/17: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.5.223.0.0/16AS2158595.223.0.0/17AS215859This prefix5.223.128.0/17AS2158595.223.8.0/21AS2158595.223.16.0/24AS2158595.223.17.0/24AS2158595.223.18.0/24AS2158595.223.19.0/24AS215859+19 more

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 5.223.0.0/17
PrefixAddressesOriginVisibility
5.223.0.0/1665.5kAS215859Hetzner Cloud - Singapore80/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 5.223.0.0/17
PrefixAddressesOriginVisibility
5.223.128.0/1732.8kAS215859Hetzner Cloud - Singapore24/80

History

  1. AS21585912th August 2026 — present
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 5.223.0.0/17 in the calculator/17 reference

Routing data derived from RouteViews MRT archives and public registry data.