bgpreport

Network · data from 2026-11-12

AS37087 Super Tech STL Limited

Registry name: Super Tech STL Limited - Super Tech STL Limited, GH · PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS37087, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS37087, 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.
41.191.97.0/24 Valid Other IRR onlyRIPE-NONAUTH 670 100% 67
196.50.28.0/22 Valid Other IRR onlyRADB 670 100% 67
41.191.96.0/24 Valid Other IRR onlyRIPE-NONAUTH 668 99% 69
41.191.98.0/24 Valid Other IRR onlyRIPE-NONAUTH 668 99% 67
41.191.99.0/24 Valid Other IRR onlyRIPE-NONAUTH 668 99% 69
41.191.96.0/22 Valid Other IRR onlyRADB, RIPE-NONAUTH 667 99% 69
196.50.28.0/24 Valid RIR databaseAFRINIC, RADB 668 99% 68
196.50.29.0/24 Valid RIR databaseAFRINIC 668 99% 68
196.50.30.0/24 Valid RIR databaseAFRINIC 668 99% 68
196.50.31.0/24 Valid RIR databaseAFRINIC 668 99% 68

AS-SET

PeeringDB's irr_as_set for AS37087: AFRINIC::AS-37087. 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 (AS37087 isn't in the set, or no route object for AS37087 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 objectsAS37087 in itNot covered
AFRINIC::AS-37087 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 7 are in fix.csv.

  • Route object: RIR6
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: RIR41.191.97.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.670 of 673
Route object: RIR196.50.28.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR41.191.96.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.668 of 673
Route object: RIR41.191.98.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.668 of 673
Route object: RIR41.191.99.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.668 of 673
Route object: RIR41.191.96.0/22Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.667 of 673
AS-SET: not foundAFRINIC::AS-37087PeeringDB names AFRINIC::AS-37087; no IRR database read has it.

Route objects not announced

Every route object with origin AS37087 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.