SUBNET.IM

167.102.236.0/23

networkMarylandAS27026

At a glance

Addresses

512

/23 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

ARINUS

Allocated 27th May 1993

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 167.102.236.0/23, fanning out from AS27026 toward the vantage points that see it. Each path is written out in full beneath the graph.AS27026networkMarylandOriginAS3356Lumen (Level 3)AS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS6939Hurricane Electri…AS132337AxclusiveAS20130Depaul UniversityAS10886University of Mar…AS6461Zayo BandwidthAS34549meerfarbig GmbH &…AS213151Christian Elsen
  1. London, UK2702633568529This path
  2. Sao Paulo270263356266213This path
  3. Singapore270266939132337This path
  4. Oregon, US27026693920130This path
  5. Amsterdam2702610886646134549213151This 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 79 of 80 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
27th May 1993
Allocation block
167.102.0.0/16
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 167.102.236.0/23: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.167.102.224.0/19AS27026167.102.0.0/16AS27026167.102.236.0/23AS27026This prefix167.102.238.0/23AS401062

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 167.102.236.0/23
PrefixAddressesOriginVisibility
167.102.224.0/198.2kAS27026networkMaryland79/80
167.102.0.0/1665.5kAS27026networkMaryland79/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 167.102.236.0/23
PrefixAddressesOriginVisibility
167.102.238.0/23512AS401062Hagerstown Community College79/80

History

  1. AS2702612th August 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 167.102.236.0/23 in the calculator/23 reference

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