subnet.im

79.127.32.0/20

At a glance

Addresses

4,096

/20 block

Visibility

1%

1 of 76 vantage points

RPKI

Invalid

Registry

RIPE NCCIR

Allocated 17th September 2007

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: 1 observed path to 79.127.32.0/20, fanning out from AS43754 toward the vantage points that see it. Each path is written out in full beneath the graph.AS43754Asiatech Data Tra…OriginAS41689Asiatech Data Tra…AS49666Telecommunication…AS33891Core-Backbone GmbHAS1299Arelion (fka. Tel…AS6762Telecom Italia Sp…AS1680Cellcom Fixed Lin…AS42013Together Communic…
  1. Oregon, US4375441689496663389112996762168042013This 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.

Route visibility

1%

Seen by 1 of 76 full-feed vantage points

Seen by few vantage points

Observed at 1 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
Iran
Allocated
17th September 2007
Allocation block
79.127.0.0/17
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 79.127.32.0/20
ROA prefixAuthorised originMax length
79.127.32.0/19AS43754/19
79.127.0.0/18AS43754/18
79.127.0.0/17AS41689/17
79.127.0.0/17AS43754/17

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 79.127.32.0/20: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.79.127.32.0/19AS4375479.127.0.0/18AS4375479.127.0.0/17AS4375479.127.32.0/20AS43754This prefix79.127.48.0/20AS4375479.127.44.0/23AS4440079.127.42.0/24AS4375479.127.46.0/24AS43415

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

More specific announcements

Sibling prefixes

Prefixes of the same length sharing a parent block with 79.127.32.0/20
PrefixAddressesOriginVisibility
79.127.48.0/204.1kAS43754Asiatech Data Transmission company76/76

History

  1. AS4375429th October 2026 — present
  2. AS4375424th October 2026 — 25th 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 79.127.32.0/20 in the calculator/20 reference

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