subnet.im

2a12:5440:7::/48

ARAAX DADEH GOSTAR information and communication Development Co (Private Joint Stock)AS51235

At a glance

Subnets

65,536 × /64

/48 block

Visibility

17%

11 of 63 vantage points

RPKI

Invalid

Registry

RIPE NCCIR

Allocated 13th January 2022

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 2a12:5440:7::/48 as seen from Singapore, read outward from the origin: AS51235 → AS42337 → AS12880 → AS49666 → AS12389 → AS8966 → AS132337. Each hop is listed with its network name beneath the graph.AS51235ARAAX DADEH GOSTA…OriginAS42337Respina Networks …AS12880Iran Information …AS49666Telecommunication…AS12389PJSC RostelecomAS8966Etisalat (E&)AS132337Axclusive

Seen from Singapore

  1. 1AS51235ARAAX DADEH GOSTAR information and communication Development Co (Private Joint Stock)IROrigin
    Peer of AS51235seen on 1,187 paths from 139 vantage points
  2. 2AS42337Respina Networks & Beyond PJSCIR
    Peer of AS42337seen on 144,214 paths from 139 vantage points
  3. 3AS12880Iran Information Technology Company PJSCIR
    Peer of AS12880seen on 175,426 paths from 139 vantage points
  4. 4AS49666Telecommunication Infrastructure CompanyIR
    Peer of AS49666seen on 37,731 paths from 127 vantage points
  5. 5AS12389PJSC RostelecomRU
    Peer of AS12389seen on 26 paths from 2 vantage points
  6. 6AS8966Etisalat (E&)AE
    Peer of AS8966seen on 155,982 paths from 2 vantage points
  7. 7AS132337AxclusiveSGVantage 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. Singapore51235423371288049666123898966132337Shown 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.

Route visibility

17%

Seen by 11 of 63 full-feed vantage points

Seen by few vantage points

Observed at 4 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
13th January 2022
Allocation block
2a12:5440::/29
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 2a12:5440:7::/48
ROA prefixAuthorised originMax length
2a12:5440::/45AS51235/45

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

No prefix of the same length in the same parent block is announced.

History

  1. AS512353rd November 2026 — present
  2. AS5123520th October 2026 — 2nd November 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.

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