subnet.im

131.222.213.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

80 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCTR

Allocated 6th April 1990

AS paths to this prefix

All paths

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

OriginVantage point · Amsterdam
One AS path to 131.222.213.0/24 as seen from Amsterdam, read outward from the origin: AS214095 → AS208972 → AS44901 → AS4849 → AS8298. Each hop is listed with its network name beneath the graph.AS214095E Sim internation…OriginAS208972GIBIRNet IletisimAS44901Belcloud LTDAS4849S3 Company LtdAS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS214095seen on 160 paths from 80 vantage points
  2. Peer of AS208972seen on 8,074 paths from 33 vantage points
  3. Peer of AS44901seen on 9,230 paths from 81 vantage points
  4. Peer of AS4849seen on 1,270 paths from 2 vantage points
  5. 5AS8298IPng Networks GmbHCHVantage 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. Singapore21409520897244901132337This path
  2. Oregon, US214095208972693920130This path
  3. Amsterdam2140952089724490148498298Shown above
  4. London, UK2140952089726204129935280This path
  5. Sao Paulo2140952089726204291435280This 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 80 of 81 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
Türkiye
Allocated
6th April 1990
Allocation block
131.222.208.0/21
Status
assigned
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 131.222.213.0/24
ROA prefixAuthorised originMax length
131.222.213.0/24AS214095/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

Prefixes of the same length sharing a parent block with 131.222.213.0/24
PrefixAddressesOriginVisibility
131.222.212.0/24256AS34984Superonline Iletisim Hizmetleri A.S.81/81

History

  1. AS21409522nd September 2026 — present
  2. AS20476712th August 2026 — 21st September 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 131.222.213.0/24 in the calculator/24 reference

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