subnet.im

209.59.31.0/24

Not announced at this prefix length

We do not see 209.59.31.0/24 announced as its own route. The most specific announcement covering it is 209.59.28.0/22, originated by AS17378 (TierPoint, LLC). Traffic to addresses in this block follows that route.

At a glance

Addresses

256

/24 block

Visibility

Unknown

RPKI

Unknown

Registry

ARINUS

Allocated 15th July 2004

AS paths to this prefix

No AS paths are stored for this prefix. We keep the full path from one reference peer per collector rather than from every peer, so a prefix only has paths here once it has been seen by one of those peers.

Registry and RPKI

RIR
ARIN — North America
Country
United States
Allocated
15th July 2004
Allocation block
209.59.0.0/19
Status
allocated
Origin validation
Unknown

ROAs covering this prefix

Route Origin Authorisations covering 209.59.31.0/24
ROA prefixAuthorised originMax length
209.59.0.0/19AS17378/24
209.59.0.0/19AS7181/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 209.59.31.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.209.59.28.0/22AS17378209.59.0.0/19AS17378209.59.31.0/24This 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 209.59.31.0/24
PrefixAddressesOriginVisibility
209.59.28.0/221kAS17378TierPoint, LLC80/81
209.59.0.0/198.2kAS17378TierPoint, LLC80/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. AS718126th September 2026 — 26th September 2026
  2. AS718125th September 2026 — 25th September 2026
  3. AS1737825th September 2026 — 25th September 2026
  4. AS1737823rd September 2026 — 24th September 2026
  5. AS718123rd September 2026 — 24th September 2026
  6. AS718122nd September 2026 — 22nd September 2026
  7. AS1737822nd September 2026 — 22nd 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 209.59.31.0/24 in the calculator/24 reference

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