bgpreport

Network · data from 2026-11-12

AS37484 Lasernet

Registry name: Lasernet (Pty) Ltd - Lasernet (Pty) Ltd, ZA · PeeringDB

33IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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 AS37484, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS37484, 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.
197.155.32.0/19 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
197.155.32.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.33.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.34.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.35.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.36.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.37.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.38.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.39.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.40.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.41.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.42.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
197.155.43.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.44.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.45.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
197.155.46.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
197.155.47.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.48.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
197.155.49.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.50.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.51.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
197.155.52.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.53.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.54.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.55.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.56.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.57.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
197.155.58.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 673 100% 66
197.155.59.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.60.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.61.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.62.0/24 Valid RIR databaseAFRINIC 673 100% 66
197.155.63.0/24 Valid RIR databaseAFRINIC 673 100% 66
2c0f:f838::/32 Valid RIR databaseAFRINIC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS37484: AS37484. 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 (AS37484 isn't in the set, or no route object for AS37484 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 objectsAS37484 in itNot covered
AS37484 A single AS number, not a set: AS37484 (this network), 34 route objects.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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