subnet.im

185.110.246.0/24

At a glance

Addresses

256

/24 block

Visibility

12%

10 of 81 vantage points

RPKI

Invalid

Registry

RIPE NCCIR

Allocated 27th July 2015

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 185.110.246.0/24 as seen from Singapore, read outward from the origin: AS213807 → AS31549 → AS49666 → AS29049 → AS6663 → AS132337. Each hop is listed with its network name beneath the graph.AS213807Fanavaran Mehr Va…OriginAS31549Aria Shatel PJSCAS49666Telecommunication…AS29049Delta Telecom LtdAS6663Türk Telekom Inte…AS132337Axclusive

Seen from Singapore

  1. Peer of AS213807seen on 3,898 paths from 81 vantage points
  2. Peer of AS31549seen on 15,914 paths from 145 vantage points
  3. Peer of AS49666seen on 300,996 paths from 81 vantage points
  4. Peer of AS29049seen on 9,914 paths from 103 vantage points
  5. Peer of AS6663seen on 4,001 paths from 2 vantage points
  6. 6AS132337AxclusiveSGVantage 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. Singapore2138073154949666290496663132337Shown 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

12%

Seen by 10 of 81 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
27th July 2015
Allocation block
185.110.244.0/22
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 185.110.246.0/24
ROA prefixAuthorised originMax length
185.110.246.0/24AS31549/24

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 185.110.246.0/24
PrefixAddressesOriginVisibility
185.110.247.0/24256AS31549Aria Shatel PJSC81/81

History

  1. AS21380722nd September 2026 — present
  2. AS3154912th 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 185.110.246.0/24 in the calculator/24 reference

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