subnet.im

66.33.37.0/24

INFINITIUM CORPORATIONAS50937

INFINITIUM CORPORATIONAS216357

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

94%

75 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 13th October 2000

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 66.33.37.0/24 as seen from Singapore, read outward from the origin: AS50937 → AS34872 → AS3214 → AS50629 → AS50263 → AS132337. Each hop is listed with its network name beneath the graph.AS50937INFINITIUM CORPOR…OriginAS34872Servperso SystemsAS3214xTom GmbHAS50629LWLcom GmbHAS50263A-Systems Sp. z o…AS132337Axclusive

Seen from Singapore

  1. Peer of AS50937seen on 148 paths from 137 vantage points
  2. Peer of AS34872seen on 3,399 paths from 92 vantage points
  3. Peer of AS3214seen on 434 paths from 40 vantage points
  4. Peer of AS50629seen on 1,519 paths from 11 vantage points
  5. Peer of AS50263seen on 8,475 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. Amsterdam5093734872213151This path
  2. London, UK50937348728529This path
  3. Oregon, US5093734872693920130This path
  4. Sao Paulo5093734872249613356266213This path
  5. Singapore509373487232145062950263132337Shown 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

94%

Seen by 75 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
United States
Allocated
13th October 2000
Allocation block
66.33.37.0/24
Status
assigned
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 66.33.37.0/24
ROA prefixAuthorised originMax length
66.33.37.0/24AS216357/24
66.33.37.0/24AS50937/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 66.33.37.0/24
PrefixAddressesOriginVisibility
66.33.36.0/24256AS13768Aptum Technologies79/80

History

  1. AS5093712th August 2026 present
  2. AS21635712th 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 66.33.37.0/24 in the calculator/24 reference

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