subnet.im

74.127.72.0/24

OTZ Telecommunications, LLCAS397893

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

ARINUS

Allocated 2nd April 2007

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 74.127.72.0/24 as seen from London, UK, read outward from the origin: AS397893 → AS7782 → AS6461 → AS8529. Each hop is listed with its network name beneath the graph.AS397893OTZ Telecommunica…OriginAS7782Alaska Communicat…AS6461Zayo BandwidthAS8529Zain Omantel Inte…

Seen from London, UK

  1. 1AS397893OTZ Telecommunications, LLCUSOrigin
    Peer of AS397893seen on 478 paths from 80 vantage points
  2. 2AS7782Alaska Communications Systems Group, Inc.US
    Peer of AS7782seen on 4,407 paths from 142 vantage points
  3. 3AS6461Zayo BandwidthUS
    Peer of AS6461seen on 45,651 paths from 2 vantage points
  4. 4AS8529Zain Omantel International FZ-LLCAEVantage 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. Amsterdam39789377826939213151This path
  2. London, UK397893778264618529Shown above
  3. Sao Paulo39789377826939266213This path
  4. Singapore39789377826939132337This path
  5. Oregon, US3978937782693920130This 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 79 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
ARIN — North America
Country
United States
Allocated
2nd April 2007
Allocation block
74.127.64.0/18
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

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 74.127.72.0/24
PrefixAddressesOriginVisibility
74.127.73.0/24256AS397893OTZ Telecommunications, LLC79/80

History

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

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