subnet.im

189.81.244.0/23

At a glance

Addresses

512

/23 block

Visibility

99%

75 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCLT

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 189.81.244.0/23 as seen from Oregon, US, read outward from the origin: AS59711 → AS9002 → AS8551 → AS42013. Each hop is listed with its network name beneath the graph.AS59711HZ Hosting LtdOriginAS9002RETN LimitedAS8551Bezeq Internation…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS59711seen on 846 paths from 96 vantage points
  2. Peer of AS9002seen on 34,421 paths from 1 vantage point
  3. Peer of AS8551seen on 1,077,002 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. London, UK5971190028529This path
  2. Amsterdam597119002250918298This path
  3. Sao Paulo597119002645335280This path
  4. Singapore597119002335623673This path
  5. Oregon, US597119002855142013Shown above

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 75 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
Lithuania
Allocated
20th February 2025
Allocation block
189.81.0.0/16
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 189.81.244.0/23
ROA prefixAuthorised originMax length
189.81.244.0/23AS59711/23

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 189.81.244.0/23
PrefixAddressesOriginVisibility
189.81.246.0/23512AS12741Netia SA75/76

History

  1. AS5971130th September 2026 — present
  2. AS20134112th 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 189.81.244.0/23 in the calculator/23 reference

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