subnet.im

163.5.50.0/24

Nexus Partners LimitedAS218232

The Infrastructure Group B.V.AS60404

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

72%

55 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCFR

Allocated 29th June 1992

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 163.5.50.0/24 as seen from Sao Paulo, read outward from the origin: AS218232 → AS60404 → AS55285 → AS1299 → AS35280. Each hop is listed with its network name beneath the graph.AS218232Nexus Partners Li…OriginAS60404The Infrastructur…AS55285Serverside.comAS1299Arelion (fka. Tel…AS35280F5 Networks SARL

Seen from Sao Paulo

  1. Peer of AS218232seen on 55 paths from 55 vantage points
  2. Peer of AS60404seen on 2,783 paths from 32 vantage points
  3. Peer of AS55285seen on 3,856 paths from 121 vantage points
  4. Peer of AS1299seen on 509,875 paths from 6 vantage points
  5. 5AS35280F5 Networks SARLFRVantage 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. Amsterdam218232604048298This path
  2. Singapore604042056223673This path
  3. London, UK2182326040469398529This path
  4. Sao Paulo2182326040455285129935280Shown above
  5. Oregon, US2182326040420562855142013This 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

72%

Seen by 55 of 76 full-feed vantage points

Partially propagated

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
France
Allocated
29th June 1992
Allocation block
163.5.0.0/16
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 163.5.50.0/24
ROA prefixAuthorised originMax length
163.5.50.0/24AS218232/24
163.5.50.0/24AS60404/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 163.5.50.0/24
PrefixAddressesOriginVisibility
163.5.51.0/24256AS219343"TTC SERVICE" LLC76/76

History

  1. AS2182328th November 2026 — present
  2. AS6040431st October 2026 — present
  3. AS19856629th October 2026 — 31st October 2026
  4. AS19856612th 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 163.5.50.0/24 in the calculator/24 reference

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