bgpreport

Network · data from 2026-11-12

AS42579 Sargasso Networks Ltd. (UK)

Registry name: SARGASSO-EU-AS Comtec Enterprises Ltd, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS42579, 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.

77.73.144.0/21 No ROA RIR databaseRIPE 673 100% 67
77.73.144.0/22 No ROA RIR databaseRIPE 673 100% 67
77.73.148.0/22 No ROA RIR databaseRIPE 673 100% 67
78.158.64.0/21 No ROA RIR databaseRIPE 673 100% 67
78.158.64.0/22 No ROA RIR databaseRIPE 673 100% 67
78.158.68.0/22 No ROA RIR databaseRIPE 673 100% 67
2a01:550::/32 No ROA RIR databaseRIPE 634 100% 67
2a01:550::/33 No ROA RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS42579: RIPE::AS-SARGASSO-UK. 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 (AS42579 isn't in the set, or no route object for AS42579 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 objectsAS42579 in itNot covered
RIPE::AS-SARGASSO-UK RIPE 74127 Yes 0

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

  • ROA: none8
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none77.73.144.0/21No ROA covers it. Add a ROA for AS42579, maxLength 21.673 of 673
ROA: none77.73.144.0/22No ROA covers it. Add a ROA for AS42579, maxLength 22.673 of 673
ROA: none77.73.148.0/22No ROA covers it. Add a ROA for AS42579, maxLength 22.673 of 673
ROA: none78.158.64.0/21No ROA covers it. Add a ROA for AS42579, maxLength 21.673 of 673
ROA: none78.158.64.0/22No ROA covers it. Add a ROA for AS42579, maxLength 22.673 of 673
ROA: none78.158.68.0/22No ROA covers it. Add a ROA for AS42579, maxLength 22.673 of 673
ROA: none2a01:550::/32No ROA covers it. Add a ROA for AS42579, maxLength 32.634 of 636
ROA: none2a01:550::/33No ROA covers it. Add a ROA for AS42579, maxLength 33.634 of 636

Route objects not announced

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

77.73.144.0/23RIPENo ROA
77.73.146.0/23RIPENo ROA
77.73.148.0/23RIPENo ROA
77.73.150.0/23RIPENo ROA
78.158.64.0/23RIPENo ROA
78.158.66.0/23RIPENo ROA
78.158.68.0/23RIPENo ROA
78.158.70.0/23RIPENo ROA
78.158.87.0/24RIPEInvalid: origin

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.