subnet.im

188.255.249.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

80 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCRS

Allocated 3rd March 2011

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.

OriginVantage points
AS path graph: 5 observed paths to 188.255.249.0/24, fanning out from AS401486 toward the vantage points that see it. Each path is written out in full beneath the graph.AS401486RAVNIX LLCOriginAS13876FiberLight, LLCAS35280F5 Networks SARLAS1299Arelion (fka. Tel…AS35280F5 Networks SARLAS6939Hurricane Electri…AS132337AxclusiveAS20130Depaul UniversityAS25091IP-Max SAAS8298IPng Networks GmbH
  1. Sao Paulo4014861387635280This path
  2. London, UK40148613876129935280This path
  3. Singapore401486138766939132337This path
  4. Oregon, US40148613876693920130This path
  5. Amsterdam401486138761299250918298This 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
Serbia
Allocated
3rd March 2011
Allocation block
188.255.128.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 188.255.249.0/24
ROA prefixAuthorised originMax length
188.255.249.0/24AS401486/24
188.255.249.0/24AS402970/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 188.255.249.0/24
PrefixAddressesOriginVisibility
188.255.248.0/24256AS9125Orion telekom d.o.o.81/81

History

  1. AS40148623rd September 2026 — present
  2. AS40297022nd September 2026 — 23rd September 2026
  3. AS21528712th 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 188.255.249.0/24 in the calculator/24 reference

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