subnet.im

83.98.192.0/24

HGC Global Communications LimitedAS9304

Smart LinkAS139642

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

28%

21 of 76 vantage points

RPKI

Invalid

Registry

RIPE NCCNL

Allocated 14th January 2004

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: 2 observed paths to 83.98.192.0/24, fanning out from AS9304, AS139642 toward the vantage points that see it. Each path is written out in full beneath the graph.AS9304HGC Global Commun…OriginAS4635HKIX Route ServersAS23673Cogetel Online, C…AS139642Smart LinkOriginAS63199CDS Global Cloud …AS9002RETN LimitedAS6762Telecom Italia Sp…AS1680Cellcom Fixed Lin…AS42013Together Communic…
  1. Singapore9304463523673This path
  2. Oregon, US1396426319990026762168042013This 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

28%

Seen by 21 of 76 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Netherlands
Allocated
14th January 2004
Allocation block
83.98.192.0/21
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 83.98.192.0/24
ROA prefixAuthorised originMax length
83.98.192.0/24AS834/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 83.98.192.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.83.98.192.0/21AS831583.98.192.0/24AS9304This prefix83.98.193.0/24AS134494

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 83.98.192.0/24
PrefixAddressesOriginVisibility
83.98.192.0/212kAS8315WorldStream B.V.6/76

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 83.98.192.0/24
PrefixAddressesOriginVisibility
83.98.193.0/24256AS134494Code For Host Inc Ltd75/76

History

  1. AS13964210th November 2026 — present
  2. AS930429th October 2026 — present
  3. AS930422nd September 2026 — 26th October 2026
  4. AS13964212th 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 83.98.192.0/24 in the calculator/24 reference

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