subnet.im

103.85.86.0/24

At a glance

Addresses

256

/24 block

Visibility

1%

1 of 78 vantage points

RPKI

Valid

Registry

APNICCN

Allocated 7th February 2017

AS paths to this prefix

All paths

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

OriginVantage point · Oregon, US
One AS path to 103.85.86.0/24 as seen from Oregon, US, read outward from the origin: AS131483 → AS153911 → AS13378 → AS17433 → AS3491 → AS6762 → AS1680 → AS42013. Each hop is listed with its network name beneath the graph.AS131483Jiangsu Dongyun C…OriginAS153911DuoTu CloudAS13378Qingye CloudAS17433Hytron Network Se…AS3491PCCW Global (HK) …AS6762Telecom Italia Sp…AS1680Cellcom Fixed Lin…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS131483seen on 2 paths from 1 vantage point
  2. Peer of AS153911seen on 2 paths from 1 vantage point
  3. Peer of AS13378seen on 461 paths from 78 vantage points
  4. Peer of AS17433seen on 9,851 paths from 139 vantage points
  5. Peer of AS3491seen on 35,650 paths from 27 vantage points
  6. Peer of AS6762seen on 33,218 paths from 1 vantage point
  7. Peer of AS1680seen on 35,557 paths from 1 vantage 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. Singapore2365041344837174100995532923673This path
  2. Oregon, US131483153911133781743334916762168042013Shown 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. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

1%

Seen by 1 of 78 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
APNIC — Asia-Pacific
Country
China
Allocated
7th February 2017
Allocation block
103.85.84.0/22
Status
allocated
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 103.85.86.0/24
ROA prefixAuthorised originMax length
103.85.84.0/22AS131483/24
103.85.84.0/22AS151300/24
103.85.84.0/22AS23650/24
103.85.84.0/22AS4837/24
103.85.84.0/22AS56046/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 103.85.86.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.103.85.86.0/23AS4837103.85.87.0/24AS23650103.85.86.0/24AS131483This prefix103.85.87.0/24AS131483

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 103.85.86.0/24
PrefixAddressesOriginVisibility
103.85.86.0/23512AS4837China Unicom Backbone8/78

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 103.85.86.0/24
PrefixAddressesOriginVisibility
103.85.87.0/24256AS23650China Telecom Jiangsu Province IDC Network1/78
103.85.87.0/24256AS131483Jiangsu Dongyun Cloud computing co., LTD1/78

History

  1. AS13148329th October 2026 — present
  2. AS236503rd November 2026 — present
  3. AS5604622nd September 2026 — 12th October 2026
  4. AS13148312th 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 103.85.86.0/24 in the calculator/24 reference

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