subnet.im

85.149.232.0/23

At a glance

Addresses

512

/23 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCVG

Allocated 6th October 2004

AS paths to this prefix

All paths

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

OriginVantage point · Sao Paulo
One AS path to 85.149.232.0/23 as seen from Sao Paulo, read outward from the origin: AS47191 → AS22427 → AS40065 → AS17476 → AS3356 → AS266213. Each hop is listed with its network name beneath the graph.AS47191blue tech technol…OriginAS22427GNET INC.AS40065CNSERVERS LLCAS17476CloudRadium (HK) …AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…

Seen from Sao Paulo

  1. Peer of AS47191seen on 719 paths from 80 vantage points
  2. Peer of AS22427seen on 1,119 paths from 80 vantage points
  3. Peer of AS40065seen on 10,989 paths from 80 vantage points
  4. Peer of AS17476seen on 1,800 paths from 15 vantage points
  5. Peer of AS3356seen on 997,311 paths from 2 vantage points

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. Singapore47191224274006517476132337This path
  2. London, UK4719122427400651747612998529This path
  3. Sao Paulo471912242740065174763356266213Shown above
  4. Oregon, US47191224274006517476693920130This path
  5. Amsterdam47191224274006517476325734549213151This 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
RIPE NCC — Europe, Middle East, Central Asia
Country
British Virgin Islands
Allocated
6th October 2004
Allocation block
85.149.224.0/20
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 85.149.232.0/23
ROA prefixAuthorised originMax length
85.149.224.0/20AS47191/24
85.149.224.0/20AS50183/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 85.149.232.0/23: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.85.149.232.0/23AS47191This prefix85.149.232.0/24AS4719185.149.233.0/24AS47191

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

No less specific announcement covers this prefix.

More specific announcements

Announcements contained within 85.149.232.0/23
PrefixAddressesOriginVisibility
85.149.232.0/24256AS47191blue tech technology Co., Limited1/80
85.149.233.0/24256AS47191blue tech technology Co., Limited1/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 85.149.232.0/23
PrefixAddressesOriginVisibility
85.149.234.0/23512AS47191blue tech technology Co., Limited79/80

History

  1. AS4719112th 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 85.149.232.0/23 in the calculator/23 reference

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