bgpreport

Network · data from 2026-11-12

AS13937 Uniserve Communications Anycast DNS

Registry name: UNISERVE-AS13937 - Uniserve On Line, CA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13937, 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.239.130.0/24 No ROA Other IRR onlyRADB 671 100% 67
204.239.131.0/24 No ROA Other IRR onlyRADB 671 100% 67
2605:1000:a::/48 No ROA Other IRR onlyRADB 635 100% 70
2605:1000:b::/48 No ROA Other IRR onlyRADB 635 100% 70

AS-SET

PeeringDB's irr_as_set for AS13937: AS-CONE:AS13937. 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 (AS13937 isn't in the set, or no route object for AS13937 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 objectsAS13937 in itNot covered
AS-CONE:AS13937 In no IRR database read today.

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

  • ROA: none4
  • Route object: RIR4
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none204.239.130.0/24No ROA covers it. Add a ROA for AS13937, maxLength 24.671 of 673
Route object: RIR204.239.130.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.239.131.0/24No ROA covers it. Add a ROA for AS13937, maxLength 24.671 of 673
Route object: RIR204.239.131.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2605:1000:a::/48No ROA covers it. Add a ROA for AS13937, maxLength 48.635 of 636
Route object: RIR2605:1000:a::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2605:1000:b::/48No ROA covers it. Add a ROA for AS13937, maxLength 48.635 of 636
Route object: RIR2605:1000:b::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
AS-SET: not foundAS-CONE:AS13937PeeringDB names AS-CONE:AS13937; no IRR database read has it.

Route objects not announced

Every route object with origin AS13937 is announced.

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.