bgpreport

Network · data from 2026-11-12

AS46652 ServerStack

Registry name: SERVERSTACK-ASN - DigitalOcean, LLC, US · PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
29Route objects not announced registered with origin AS46652, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS46652, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

141.0.168.0/24 Valid Other IRR onlyRADB 672 100% 66
141.0.171.0/24 Valid Other IRR onlyRADB 672 100% 66
141.0.172.0/22 Valid Other IRR onlyRADB 672 100% 66
141.0.174.0/24 Valid Other IRR onlyRADB 672 100% 66
185.88.180.0/22 Valid Other IRR onlyRADB 672 100% 66
199.4.223.0/24 Valid Other IRR onlyRADB 672 100% 66
69.55.53.0/24 Valid RIR databaseARIN, RADB 672 100% 66
69.55.57.0/24 Valid RIR databaseARIN, RADB 672 100% 66

AS-SET

PeeringDB's irr_as_set for AS46652: AS46652. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS46652 isn't in the set, or no route object for AS46652 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS46652 in itNot covered
AS46652 A single AS number, not a set: AS46652 (this network), 37 route objects.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 35 are in fix.csv.

  • Route object: RIR6
  • Route object: not announced29
ChangePrefix or setDetailFull-table peers
Route object: RIR141.0.168.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR141.0.171.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR141.0.172.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR141.0.174.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR185.88.180.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR199.4.223.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS46652 whose prefix no peer sees AS46652 announce. Many are kept on purpose (backup routes, space announced only in some places).

69.55.48.0/20ARINValid
69.55.48.0/21ARINValid
69.55.48.0/22ARIN, RADBValid
69.55.48.0/23ARINValid
69.55.48.0/24ARINValid
69.55.49.0/24ARINValid
69.55.50.0/23ARINValid
69.55.50.0/24ARINValid
69.55.51.0/24ARINValid
69.55.52.0/22ARINValid
69.55.52.0/23ARINValid
69.55.52.0/24ARIN, RADBValid
69.55.54.0/23ARIN, RADBValid
69.55.54.0/24ARINValid
69.55.55.0/24ARINValid
69.55.56.0/21ARINValid
69.55.56.0/22ARINValid
69.55.56.0/23ARINValid
69.55.56.0/24ARINValid
69.55.58.0/23ARIN, RADBValid
69.55.58.0/24ARINValid
69.55.59.0/24ARINValid
69.55.60.0/22ARIN, RADBValid
69.55.60.0/23ARINValid
69.55.60.0/24ARINValid
69.55.61.0/24ARINValid
69.55.62.0/23ARINValid
69.55.62.0/24ARINValid
69.55.63.0/24ARINValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.