bgpreport

Network · data from 2026-11-12

AS42845 Bretagne Telecom

Registry name: Bretagnetelecom BLUE SAS, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS42845, 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.
193.104.205.0/24 No ROA RIR databaseRIPE 669 99% 67
185.87.92.0/22 Valid None 669 99% 67
37.157.224.0/21 Valid RIR databaseRIPE 669 99% 67
37.157.224.0/24 Valid RIR databaseRIPE 669 99% 67
37.157.225.0/24 Valid RIR databaseRIPE 669 99% 67
37.157.226.0/24 Valid RIR databaseRIPE 669 99% 67
37.157.227.0/24 Valid RIR databaseRIPE 669 99% 67
37.157.228.0/24 Valid RIR databaseRIPE 669 99% 67
37.157.229.0/24 Valid RIR databaseRIPE 669 99% 67
37.157.230.0/24 Valid RIR databaseRIPE 669 99% 67
37.157.231.0/24 Valid RIR databaseRIPE 669 99% 67
45.137.144.0/22 Valid RIR databaseRIPE 669 99% 67
77.74.208.0/21 Valid RIR databaseRIPE 669 99% 67
89.46.96.0/22 Valid RIR databaseRIPE 669 99% 67
95.128.144.0/21 Valid RIR databaseRIPE 669 99% 67
95.128.144.0/24 Valid RIR databaseRIPE 669 99% 67
95.128.145.0/24 Valid RIR databaseRIPE 669 99% 67
95.128.146.0/24 Valid RIR databaseRIPE 669 99% 67
95.128.147.0/24 Valid RIR databaseRIPE 669 99% 67
95.128.148.0/24 Valid RIR databaseRIPE 669 99% 67
95.128.149.0/24 Valid RIR databaseRIPE 669 99% 67
95.128.150.0/24 Valid RIR databaseRIPE 669 99% 67
95.128.151.0/24 Valid RIR databaseRIPE 669 99% 67
149.255.48.0/21 Valid RIR databaseRIPE 669 99% 67
185.40.224.0/22 Valid RIR databaseRIPE 669 99% 67
185.87.92.0/24 Valid RIR databaseRIPE 669 99% 67
185.87.93.0/24 Valid RIR databaseRIPE 669 99% 67
185.87.94.0/24 Valid RIR databaseRIPE 669 99% 67
185.87.95.0/24 Valid RIR databaseRIPE 669 99% 67
185.135.124.0/22 Valid RIR databaseRIPE 669 99% 67
185.185.116.0/22 Valid RIR databaseRIPE 669 99% 67
185.232.224.0/22 Valid RIR databaseRIPE 669 99% 67
193.28.233.0/24 Valid RIR databaseRIPE 669 99% 67
194.150.92.0/22 Valid RIR databaseRIPE 669 99% 67
77.74.208.0/24 Valid RIR databaseRIPE 668 99% 67
77.74.209.0/24 Valid RIR databaseRIPE 668 99% 67
77.74.210.0/24 Valid RIR databaseRIPE 668 99% 67
77.74.211.0/24 Valid RIR databaseRIPE 668 99% 67
77.74.212.0/24 Valid RIR databaseRIPE 668 99% 67
77.74.213.0/24 Valid RIR databaseRIPE 668 99% 67
77.74.214.0/24 Valid RIR databaseRIPE 668 99% 67
77.74.215.0/24 Valid RIR databaseRIPE 668 99% 67
2a00:7200::/32 Valid RIR databaseRIPE 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS42845: AS42845:AS-BRETAGNE_TELECOM. 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 (AS42845 isn't in the set, or no route object for AS42845 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 objectsAS42845 in itNot covered
AS42845:AS-BRETAGNE_TELECOM RIPE 8162 Yes 1

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

  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none193.104.205.0/24No ROA covers it. Add a ROA for AS42845, maxLength 24.669 of 673
Route object: none185.87.92.0/22No route object for it. Add a route object with origin AS42845 in the RIR database for the space.669 of 673

Route objects not announced

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