bgpreport

Network · data from 2026-11-12

AS263578 FacNet Telecom

Registry name: AS263578 - FacNet Telecom, BR · PeeringDB

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

Announced routes

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

179.109.64.0/20 Valid Other IRR onlyALTDB, TC 671 100% 67
2804:f4c::/32 Valid Other IRR onlyALTDB, TC 633 100% 69
179.109.72.0/21 Valid Other IRR onlyALTDB 97 14% 39
179.109.64.0/21 Valid Other IRR onlyALTDB 96 14% 39
179.109.64.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.65.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.66.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.67.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.68.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.69.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.70.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.71.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.72.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.73.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.74.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.75.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.76.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.77.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.78.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
179.109.79.0/24 Valid Other IRR onlyALTDB, RADB 2 0%low visibility 2
2804:f4c::/34 Valid Other IRR onlyALTDB, TC 2 0%low visibility 2
2804:f4c:4000::/34 Valid Other IRR onlyALTDB, TC 2 0%low visibility 2
2804:f4c:8000::/34 Valid Other IRR onlyALTDB, TC 2 0%low visibility 2
2804:f4c:c000::/34 Valid Other IRR onlyALTDB, TC 2 0%low visibility 2

AS-SET

AS263578'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 62 are in fix.csv.

  • Route object: RIR24
  • Route object: not announced38
ChangePrefix or setDetailFull-table peers
Route object: RIR179.109.64.0/20Route object only in ALTDB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:f4c::/32Route object only in ALTDB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR179.109.72.0/21Route object only in ALTDB. Add it in the RIR database for the space.97 of 673
Route object: RIR179.109.64.0/21Route object only in ALTDB. Add it in the RIR database for the space.96 of 673
Route object: RIR179.109.64.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.65.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.66.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.67.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.68.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.69.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.70.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.71.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.72.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.73.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.74.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.75.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.76.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.77.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.78.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR179.109.79.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR2804:f4c::/34Route object only in ALTDB, TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:f4c:4000::/34Route object only in ALTDB, TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:f4c:8000::/34Route object only in ALTDB, TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:f4c:c000::/34Route object only in ALTDB, TC. Add it in the RIR database for the space.2 of 636

Route objects not announced

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

179.109.64.0/22ALTDB, RADBValid
179.109.64.0/23ALTDBValid
179.109.66.0/23ALTDBValid
179.109.68.0/22ALTDBValid
179.109.68.0/23ALTDBValid
179.109.70.0/23ALTDBValid
179.109.72.0/22ALTDBValid
179.109.72.0/23ALTDBValid
179.109.74.0/23ALTDBValid
179.109.76.0/22ALTDBValid
179.109.76.0/23ALTDBValid
179.109.78.0/23ALTDBValid
2804:f4c::/33ALTDB, TCValid
2804:f4c::/35ALTDB, TCValid
2804:f4c::/36ALTDB, TCValid
2804:f4c:1000::/36ALTDB, TCValid
2804:f4c:2000::/35ALTDB, TCValid
2804:f4c:2000::/36ALTDB, TCValid
2804:f4c:3000::/36ALTDB, TCValid
2804:f4c:4000::/35ALTDB, TCValid
2804:f4c:4000::/36ALTDB, TCValid
2804:f4c:5000::/36ALTDB, TCValid
2804:f4c:6000::/35ALTDB, TCValid
2804:f4c:6000::/36ALTDB, TCValid
2804:f4c:7000::/36ALTDB, TCValid
2804:f4c:8000::/33ALTDB, TCValid
2804:f4c:8000::/35ALTDB, TCValid
2804:f4c:8000::/36ALTDB, TCValid
2804:f4c:9000::/36ALTDB, TCValid
2804:f4c:a000::/35ALTDB, TCValid
2804:f4c:a000::/36ALTDB, TCValid
2804:f4c:b000::/36ALTDB, TCValid
2804:f4c:c000::/35ALTDB, TCValid
2804:f4c:c000::/36ALTDB, TCValid
2804:f4c:d000::/36ALTDB, TCValid
2804:f4c:e000::/35ALTDB, TCValid
2804:f4c:e000::/36ALTDB, TCValid
2804:f4c:f000::/36ALTDB, TCValid

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.