bgpreport

Network · data from 2026-11-12

AS57948 COBALT Cobalt Group BV

Registry name: COBALT Cobalt Group BV, BE · not in PeeringDB

10IPv4 routes 60.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
4No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
19Route objects not announced registered with origin AS57948, seen from no peer

Announced routes

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

195.253.208.0/24 No ROA RIR databaseRIPE 671 100% 67
195.253.209.0/24 No ROA RIR databaseRIPE 671 100% 67
195.253.210.0/24 No ROA RIR databaseRIPE 671 100% 67
195.253.211.0/24 No ROA RIR databaseRIPE 671 100% 67
2.57.40.0/24 Valid RIR databaseRIPE 671 100% 67
2.57.41.0/24 Valid RIR databaseRIPE 671 100% 67
2.57.42.0/24 Valid RIR databaseRIPE 671 100% 67
91.236.244.0/24 Valid RIR databaseRIPE 671 100% 67
91.236.245.0/24 Valid RIR databaseRIPE 671 100% 67
185.70.44.0/24 Valid RIR databaseRIPE 671 100% 67
2a05:2600::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

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

  • ROA: none4
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: none195.253.208.0/24No ROA covers it. Add a ROA for AS57948, maxLength 24.671 of 673
ROA: none195.253.209.0/24No ROA covers it. Add a ROA for AS57948, maxLength 24.671 of 673
ROA: none195.253.210.0/24No ROA covers it. Add a ROA for AS57948, maxLength 24.671 of 673
ROA: none195.253.211.0/24No ROA covers it. Add a ROA for AS57948, maxLength 24.671 of 673

Route objects not announced

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

2.57.40.0/22RIPEValid
2.57.43.0/24RIPEValid
46.19.7.0/24RIPENo ROA
91.236.244.0/23RIPEValid
95.214.28.0/24RIPEInvalid: origin
95.214.29.0/24RIPEInvalid: origin
95.214.30.0/24RIPEInvalid: origin
95.214.31.0/24RIPEInvalid: origin
171.25.229.0/24RIPEValid
185.70.44.0/22RIPEValid
185.70.45.0/24RIPEValid
185.70.46.0/24RIPEValid
185.70.47.0/24RIPEValid
2a05:2600::/32RIPEValid
2a05:2601::/32RIPEValid
2a05:2602::/32RIPEValid
2a05:2603::/32RIPEValid
2a05:2604::/32RIPEValid
2a05:2607::/32RIPEValid

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.