bgpreport

Network · data from 2026-11-12

AS49477 eTF1

Registry name: E-TF1 E-TF1 SAS, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS49477, 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.
2a04:1f40::/32 Valid Nonecovered by 2a04:1f40::/29 605 95% 67
185.22.116.0/22 Valid RIR databaseRIPE 671 100% 67
193.169.66.0/23 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS49477's PeeringDB record names no 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 2 are in fix.csv.

  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2a04:1f40::/32No route object for it. A route object for 2a04:1f40::/29 with origin AS49477 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49477 in the RIR database for the space.605 of 636

Route objects not announced

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

2a04:1f40::/29RIPEValid

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.