bgpreport

Network · data from 2026-11-12

AS7905 SOONER-AS - Sooner Technology

Registry name: SOONER-AS - Sooner Technology, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS7905, 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.
143.187.0.0/16 Invalid: origin None 2 0%low visibility 2
143.187.5.0/24 Invalid: origin None 2 0%low visibility 2
204.69.233.0/24 No ROA Other IRR onlyRADB 673 100% 67
206.225.56.0/23 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

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

  • ROA: origin2
  • ROA: none2
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin143.187.0.0/16An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS7905 should announce it, add a ROA for AS7905.2 of 673
Route object: none143.187.0.0/16No route object for it. Add a route object with origin AS7905 in the RIR database for the space.2 of 673
ROA: origin143.187.5.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS7905 should announce it, add a ROA for AS7905.2 of 673
Route object: none143.187.5.0/24No route object for it. Add a route object with origin AS7905 in the RIR database for the space.2 of 673
ROA: none204.69.233.0/24No ROA covers it. Add a ROA for AS7905, maxLength 24.673 of 673
Route object: RIR204.69.233.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none206.225.56.0/23No ROA covers it. Add a ROA for AS7905, maxLength 23.673 of 673
Route object: RIR206.225.56.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

204.17.133.0/24RADBNo 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.