bgpreport

Network · data from 2026-11-12

AS8029 MSERVE-AS - Microserve, Inc.

Registry name: MSERVE-AS - Microserve, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8029, 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.

204.141.20.0/22 Invalid: origin None 62 9%low visibility 34
204.141.116.0/22 Invalid: origin None 62 9%low visibility 34

AS-SET

AS8029 isn't in PeeringDB, where networks name their AS-SET.

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 20 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: origin204.141.20.0/22ROAs covering it name AS2914, not AS8029. If AS8029 should announce it, add a ROA for AS8029.62 of 673
Route object: none204.141.20.0/22No route object for it. Add a route object with origin AS8029 in the RIR database for the space.62 of 673
ROA: origin204.141.116.0/22ROAs covering it name AS2914, not AS8029. If AS8029 should announce it, add a ROA for AS8029.62 of 673
Route object: none204.141.116.0/22No route object for it. Add a route object with origin AS8029 in the RIR database for the space.62 of 673

Route objects not announced

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

8.10.65.0/24RADBNo ROA
8.10.66.0/23RADBNo ROA
8.10.68.0/23RADBNo ROA
8.10.70.0/23RADBNo ROA
8.11.249.0/24RADBNo ROA
8.11.252.0/23RADBNo ROA
8.11.254.0/23RADBNo ROA
8.14.64.0/23RADBNo ROA
8.14.66.0/24RADBNo ROA
8.14.68.0/24RADBNo ROA
8.14.69.0/24RADBNo ROA
8.14.70.0/23RADBNo ROA
8.22.188.0/23RADBNo ROA
38.107.76.0/23RADBNo ROA
38.109.77.0/24RADBNo ROA
66.117.112.0/20RADBNo ROA

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.