subnet.im

192.6.90.0/24

Ping Technology Labs LTDAS199856

At a glance

Addresses

256

/24 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 26th August 1983

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 192.6.90.0/24, fanning out from AS199856 toward the vantage points that see it. Each path is written out in full beneath the graph.AS199856Ping Technology L…OriginAS397373H4Y Technologies …AS6939Hurricane Electri…AS8298IPng Networks GmbHAS6461Zayo BandwidthAS8529Zain Omantel Inte…AS35280F5 Networks SARLAS23673Cogetel Online, C…AS8551Bezeq Internation…AS42013Together Communic…
  1. Amsterdam19985639737369398298This path
  2. London, UK19985639737364618529This path
  3. Sao Paulo199856397373693935280This path
  4. Singapore199856397373693923673This path
  5. Oregon, US1998563973736461855142013This 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

100%

Seen by 76 of 76 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
ARIN — North America
Country
United States
Allocated
26th August 1983
Allocation block
192.6.90.0/23
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 192.6.90.0/24
ROA prefixAuthorised originMax length
192.6.90.0/24AS199856/24
192.6.90.0/24AS397373/24
192.6.90.0/23AS834/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 192.6.90.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.192.6.90.0/23AS9304192.6.90.0/24AS199856This prefix192.6.91.0/24AS397373

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 192.6.90.0/24
PrefixAddressesOriginVisibility
192.6.90.0/23512AS9304HGC Global Communications Limited1/76

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 192.6.90.0/24
PrefixAddressesOriginVisibility
192.6.91.0/24256AS397373H4Y Technologies LLC76/76

History

  1. AS19985624th October 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 192.6.90.0/24 in the calculator/24 reference

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