bgpreport

Network · data from 2026-11-12

AS32771 DNSIMPLE - DNSimple Corporation

Registry name: DNSIMPLE - DNSimple Corporation, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS32771, 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.
2001:1838:7004::/48 No ROA Other origin only 636 100% 69
199.247.153.0/24 Valid Other IRR onlyRADB 669 99% 67
199.247.155.0/24 Valid Other IRR onlyRADB 669 99% 67
2620:111:800a::/48 Valid Other IRR onlyRADB 636 100% 67
2620:111:800b::/48 Valid Other IRR onlyRADB 636 100% 67
2620:111:800c::/48 Valid Other IRR onlyRADB 636 100% 67
2620:111:800d::/48 Valid Other IRR onlyRADB 636 100% 67
2620:111:8005::/48 Valid Other IRR onlyRADB 634 100% 69
2620:111:8007::/48 Valid Other IRR onlyRADB 634 100% 69
167.94.34.0/24 Valid RIR databaseARIN, NTTCOM, RADB 673 100% 67
199.247.152.0/24 Valid RIR databaseARIN 669 99% 67
199.247.154.0/24 Valid RIR databaseARIN 669 99% 67
2620:111:8004::/48 Valid RIR databaseARIN, RADB 634 100% 69
2620:111:8006::/48 Valid RIR databaseARIN 634 100% 69

AS-SET

AS32771 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: none1
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none2001:1838:7004::/48No ROA covers it. Add a ROA for AS32771, maxLength 48.636 of 636
Route object: none2001:1838:7004::/48Route objects for it name AS23352. Add a route object with origin AS32771 in the RIR database for the space.636 of 636
Route object: RIR199.247.153.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR199.247.155.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2620:111:800a::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2620:111:800b::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2620:111:800c::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2620:111:800d::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2620:111:8005::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2620:111:8007::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

50.31.242.0/24NTTCOM, RADB, REACHNo ROA
50.31.243.0/24NTTCOM, RADB, REACHNo ROA
198.241.10.0/24NTTCOM, RADB, REACHValid
198.241.11.0/24NTTCOM, RADB, REACHValid
2620:111:8000::/44NTTCOM, RADBNo ROA
2620:111:8000::/48RADBValid
2620:111:8001::/48RADBValid
2620:111:8002::/48RADBValid
2620:111:8003::/48RADBValid
2620:111:800f::/48RADBValid

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.