bgpreport

Network · data from 2026-11-12

AS36614 SD GOVERNMENT-INC - SD Government

Registry name: SD GOVERNMENT-INC - SD Government, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36614, 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.246.18.0/24 Valid None 669 99% 67
206.124.168.0/24 Valid None 669 99% 67
206.124.170.0/24 Valid None 669 99% 67
206.124.182.0/24 Valid None 669 99% 67
204.246.16.0/23 Valid Other IRR onlyRADB 673 100% 67
204.246.20.0/24 Valid Other IRR onlyRADB 673 100% 67
204.246.28.0/24 Valid Other IRR onlyRADB 673 100% 67
204.246.31.0/24 Valid Other IRR onlyRADB 673 100% 67
206.124.160.0/24 Valid Other IRR onlyRADB 673 100% 67
206.124.174.0/24 Valid Other IRR onlyRADB 673 100% 67
206.124.175.0/24 Valid Other IRR onlyRADB 673 100% 67
206.124.176.0/22 Valid Other IRR onlyRADB 673 100% 67
206.124.180.0/24 Valid Other IRR onlyRADB 673 100% 67
206.124.181.0/24 Valid Other IRR onlyRADB 673 100% 67
204.246.19.0/24 Valid Other IRR onlyRADB 669 99% 67
206.124.164.0/24 Valid Other IRR onlyRADB 669 99% 67
206.124.165.0/24 Valid Other IRR onlyRADB 669 99% 67
206.124.184.0/22 Valid Other IRR onlyRADB 669 99% 67
206.124.191.0/24 Valid Other IRR onlyRADB 669 99% 67
204.246.22.0/24 Valid Other IRR onlyRADB 668 99% 67
204.246.23.0/24 Valid Other IRR onlyRADB 668 99% 67

AS-SET

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

  • Route object: none4
  • Route object: RIR17
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
Route object: none204.246.18.0/24No route object for it. Add a route object with origin AS36614 in the RIR database for the space.669 of 673
Route object: none206.124.168.0/24No route object for it. Add a route object with origin AS36614 in the RIR database for the space.669 of 673
Route object: none206.124.170.0/24No route object for it. Add a route object with origin AS36614 in the RIR database for the space.669 of 673
Route object: none206.124.182.0/24No route object for it. Add a route object with origin AS36614 in the RIR database for the space.669 of 673
Route object: RIR204.246.16.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR204.246.20.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR204.246.28.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR204.246.31.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR206.124.160.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR206.124.174.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR206.124.175.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR206.124.176.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR206.124.180.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR206.124.181.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR204.246.19.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR206.124.164.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR206.124.165.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR206.124.184.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR206.124.191.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR204.246.22.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR204.246.23.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

8.15.152.0/22RADBNo ROA
8.35.84.0/22RADBNo ROA
63.110.124.0/22RADBNo ROA
63.117.116.0/22RADBNo ROA
64.20.58.0/23RADBNo ROA
68.168.210.0/24RADBNo ROA
76.164.194.0/23RADBNo ROA
204.246.24.0/24RADBValid
204.246.25.0/24RADBValid
204.246.26.0/24RADBValid
204.246.27.0/24RADBValid
204.246.29.0/24RADBValid
204.246.30.0/24RADBValid
206.124.161.0/24RADBValid
206.124.172.0/24RADBValid

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.