bgpreport

Network · data from 2026-11-12

AS939 NovoServe LLC

Registry name: USA-2022 - NovoServe LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS939, 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.
205.142.240.0/23 No ROA RIR databaseARIN 672 100% 67
2606:f340::/32 No ROA RIR databaseARIN 635 100% 67
45.152.192.0/22 Valid RIR databaseRIPE 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS939: ARIN::AS-NOVOSERVE-LLC. 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 (AS939 isn't in the set, or no route object for AS939 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 objectsAS939 in itNot covered
ARIN::AS-NOVOSERVE-LLC ARIN 82332 Yes 0

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

  • ROA: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none205.142.240.0/23No ROA covers it. Add a ROA for AS939, maxLength 23.672 of 673
ROA: none2606:f340::/32No ROA covers it. Add a ROA for AS939, maxLength 32.635 of 636

Route objects not announced

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

89.105.196.0/24RIPEInvalid: origin

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.