subnet.im

203.194.56.0/24

AAPT LimitedAS9942

At a glance

Addresses

256

/24 block

Visibility

99%

80 of 81 vantage points

RPKI

No ROA

Registry

APNICAU

Allocated 12th May 2000

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 203.194.56.0/24, fanning out from AS9942 toward the vantage points that see it. Each path is written out in full beneath the graph.AS9942AAPT LimitedOriginAS2764AAPT LimitedAS4826Vocus Connect Int…AS35280F5 Networks SARLAS132337AxclusiveAS1299Arelion (fka. Tel…AS35280F5 Networks SARLAS6939Hurricane Electri…AS20130Depaul UniversityAS25091IP-Max SAAS8298IPng Networks GmbH
  1. Sao Paulo99422764482635280This path
  2. Singapore994227644826132337This path
  3. London, UK994227644826129935280This path
  4. Oregon, US994227644826693920130This path
  5. Amsterdam9942276448261299250918298This 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 80 of 81 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
APNIC — Asia-Pacific
Country
Australia
Allocated
12th May 2000
Allocation block
203.194.56.0/24
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 203.194.56.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.203.194.56.0/22AS9942203.194.0.0/18AS7545203.194.56.0/24AS9942This prefix

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 203.194.56.0/24
PrefixAddressesOriginVisibility
203.194.56.0/221kAS9942AAPT Limited80/81
203.194.0.0/1816.4kAS7545TPG Telecom Limited80/81

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS994222nd September 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 203.194.56.0/24 in the calculator/24 reference

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