subnet.im

98.97.79.0/24

At a glance

Addresses

256

/24 block

Visibility

62%

48 of 77 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 28th June 2021

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 98.97.79.0/24 as seen from Singapore, read outward from the origin: AS14593 → AS37662 → AS24482 → AS38623 → AS23673. Each hop is listed with its network name beneath the graph.AS14593SpaceX StarlinkOriginAS37662West Indian Ocean…AS24482SG.GSAS38623Metfone (Viettel …AS23673Cogetel Online, C…

Seen from Singapore

  1. Peer of AS14593seen on 12,054 paths from 140 vantage points
  2. Peer of AS37662seen on 694 paths from 4 vantage points
  3. Peer of AS24482seen on 26,088 paths from 1 vantage point
  4. Peer of AS38623seen on 86,002 paths from 1 vantage 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. Amsterdam14593376628298This path
  2. London, UK14593376628529This path
  3. Sao Paulo145933766235280This path
  4. Oregon, US1459337662693920130This path
  5. Singapore1459337662244823862323673Shown 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

62%

Seen by 48 of 77 full-feed vantage points

Partially 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
28th June 2021
Allocation block
98.97.0.0/17
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 98.97.79.0/24
ROA prefixAuthorised originMax length
98.97.0.0/17AS14593/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 98.97.79.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.98.97.78.0/23AS1459398.97.79.0/24AS14593This 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 98.97.79.0/24
PrefixAddressesOriginVisibility
98.97.78.0/23512AS14593SpaceX Starlink77/77

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. AS1459315th October 2026 — present
  2. AS1459314th October 2026 — 14th October 2026
  3. AS1459313th October 2026 — 13th October 2026
  4. AS145934th October 2026 — 4th October 2026
  5. AS1459329th September 2026 — 29th September 2026
  6. AS1459328th September 2026 — 28th September 2026
  7. AS1459327th September 2026 — 27th September 2026
  8. AS1459326th September 2026 — 26th 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 98.97.79.0/24 in the calculator/24 reference

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