subnet.im

191.44.99.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCPL

Allocated 20th February 2025

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 191.44.99.0/24 as seen from Oregon, US, read outward from the origin: AS215197 → AS58010 → AS8551 → AS42013. Each hop is listed with its network name beneath the graph.AS215197Zero Services GmbHOriginAS58010uvensys GmbHAS8551Bezeq Internation…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS215197seen on 615 paths from 76 vantage points
  2. Peer of AS58010seen on 44 paths from 1 vantage point
  3. Peer of AS8551seen on 1,076,486 paths from 1 vantage 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. Amsterdam215197580108298This path
  2. London, UK215197580108529This path
  3. Sao Paulo21519758010423035280This path
  4. Oregon, US21519758010855142013Shown above
  5. Singapore215197445926453349123673This 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

100%

Seen by 76 of 76 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
Poland
Allocated
20th February 2025
Allocation block
191.44.64.0/18
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 191.44.99.0/24
ROA prefixAuthorised originMax length
191.44.99.0/24AS215197/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 191.44.99.0/24
PrefixAddressesOriginVisibility
191.44.98.0/24256AS141750PC Cloud76/76

History

  1. AS2151973rd November 2026 — present
  2. AS1627629th October 2026 — 3rd November 2026
  3. AS1627612th August 2026 — 19th 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 191.44.99.0/24 in the calculator/24 reference

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