bgpreport

Network · data from 2026-11-12

AS267211 AS267211 - Fournet One Servicos de Comunicacao e Informatica

Registry name: AS267211 - Fournet One Servicos de Comunicacao e Informatica, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267211, 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.
2804:49f8::/33 Valid Nonecovered by 2804:49f8::/32 353 56% 65
45.231.120.0/22 Valid Other IRR onlyRADB, TC 669 99% 67
2804:49f8::/32 Valid Other IRR onlyRADB, TC 356 56% 65
2804:49f8:8000::/33 Valid Other IRR onlyTC 353 56% 65
45.231.120.0/24 Valid Other IRR onlyRADB, TC 8 1%low visibility 7
45.231.121.0/24 Valid Other IRR onlyRADB, TC 8 1%low visibility 7
45.231.122.0/23 Valid Other IRR onlyRADB, TC 5 1%low visibility 5
45.231.120.0/23 Valid Other IRR onlyRADB, TC 4 1%low visibility 3
45.231.122.0/24 Valid Other IRR onlyRADB, TC 3 0%low visibility 3
45.231.123.0/24 Valid Other IRR onlyRADB, TC 3 0%low visibility 3

AS-SET

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

  • Route object: none1
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
Route object: none2804:49f8::/33No route object for it. A route object for 2804:49f8::/32 with origin AS267211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267211 in the RIR database for the space.353 of 636
Route object: RIR45.231.120.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:49f8::/32Route object only in RADB, TC. Add it in the RIR database for the space.356 of 636
Route object: RIR2804:49f8:8000::/33Route object only in TC. Add it in the RIR database for the space.353 of 636
Route object: RIR45.231.120.0/24Route object only in RADB, TC. Add it in the RIR database for the space.8 of 673
Route object: RIR45.231.121.0/24Route object only in RADB, TC. Add it in the RIR database for the space.8 of 673
Route object: RIR45.231.122.0/23Route object only in RADB, TC. Add it in the RIR database for the space.5 of 673
Route object: RIR45.231.120.0/23Route object only in RADB, TC. Add it in the RIR database for the space.4 of 673
Route object: RIR45.231.122.0/24Route object only in RADB, TC. Add it in the RIR database for the space.3 of 673
Route object: RIR45.231.123.0/24Route object only in RADB, TC. Add it in the RIR database for the space.3 of 673

Route objects not announced

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