SUBNET.IM

177.177.2.0/23

At a glance

Addresses

512

/23 block

Visibility

24%

19 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCAE

Allocated 6th March 2025

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: 3 observed paths to 177.177.2.0/23, fanning out from AS35487 toward the vantage points that see it. Each path is written out in full beneath the graph.AS35487Misaka Network, I…OriginAS917Misaka Network, I…AS213151Christian ElsenAS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul University
  1. Amsterdam35487917213151This path
  2. Singapore35487917132337This path
  3. Oregon, US35487917693920130This 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

24%

Seen by 19 of 80 full-feed vantage points

Seen by few vantage points

Observed at 3 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
United Arab Emirates
Allocated
6th March 2025
Allocation block
177.177.0.0/19
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 177.177.2.0/23
ROA prefixAuthorised originMax length
177.177.0.0/19AS35487/32

Prefix hierarchy

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

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 177.177.2.0/23
PrefixAddressesOriginVisibility
177.177.0.0/23512AS35487Misaka Network, Inc.80/80

History

  1. AS3548712th 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 177.177.2.0/23 in the calculator/23 reference

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