SUBNET.IM

91.225.56.0/24

TOV company M-TelAS44664

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCUA

Allocated 31st January 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 91.225.56.0/24, fanning out from AS44664 toward the vantage points that see it. Each path is written out in full beneath the graph.AS44664TOV company M-TelOriginAS25133LLC "McLaut-Inves…AS8529Zain Omantel Inte…AS6939Hurricane Electri…AS213151Christian ElsenAS266213PLANETCLICK TELEC…AS50263A-Systems Sp. z o…AS132337AxclusiveAS20130Depaul University
  1. London, UK44664251338529This path
  2. Amsterdam44664251336939213151This path
  3. Sao Paulo44664251336939266213This path
  4. Singapore446642513350263132337This path
  5. Oregon, US4466425133693920130This 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 80 of 80 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
Ukraine
Allocated
31st January 2011
Allocation block
91.225.56.0/22
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 91.225.56.0/24
ROA prefixAuthorised originMax length
91.225.56.0/24AS44664/24
91.225.56.0/22AS44664/22

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 91.225.56.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.91.225.56.0/22AS4466491.225.56.0/24AS44664This prefix91.225.57.0/24AS44664

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 91.225.56.0/24
PrefixAddressesOriginVisibility
91.225.56.0/221kAS44664TOV company M-Tel80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 91.225.56.0/24
PrefixAddressesOriginVisibility
91.225.57.0/24256AS44664TOV company M-Tel80/80

History

  1. AS4466412th 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 91.225.56.0/24 in the calculator/24 reference

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