bgpreport

Network · data from 2026-11-12

AS265244 MFT Servicos de Internet Comercio e Telefonia Ltda

Registry name: AS265244 - Mafra Telecom, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265244, 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:2ccc::/36 Valid Nonecovered by 2804:2ccc::/35 634 100% 67
2804:2ccc:1000::/36 Valid Nonecovered by 2804:2ccc::/35 634 100% 67
168.0.36.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
168.0.38.0/23 Valid Other IRR onlyTC 670 100% 67
2804:2ccc::/32 Valid Other IRR onlyRADB, TC 634 100% 67
2804:2ccc::/35 Valid Other IRR onlyRADB, TC 634 100% 67
168.0.36.0/24 Valid Other IRR onlyRADB, TC 201 30% 56
168.0.39.0/24 Valid Other IRR onlyTC 201 30% 56
168.0.37.0/24 Valid Other IRR onlyRADB, TC 200 30% 56
168.0.38.0/24 Valid Other IRR onlyRADB, TC 200 30% 56

AS-SET

AS265244'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 24 are in fix.csv.

  • Route object: none2
  • Route object: RIR8
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
Route object: none2804:2ccc::/36No route object for it. A route object for 2804:2ccc::/35 with origin AS265244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265244 in the RIR database for the space.634 of 636
Route object: none2804:2ccc:1000::/36No route object for it. A route object for 2804:2ccc::/35 with origin AS265244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265244 in the RIR database for the space.634 of 636
Route object: RIR168.0.36.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.0.38.0/23Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:2ccc::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:2ccc::/35Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR168.0.36.0/24Route object only in RADB, TC. Add it in the RIR database for the space.201 of 673
Route object: RIR168.0.39.0/24Route object only in TC. Add it in the RIR database for the space.201 of 673
Route object: RIR168.0.37.0/24Route object only in RADB, TC. Add it in the RIR database for the space.200 of 673
Route object: RIR168.0.38.0/24Route object only in RADB, TC. Add it in the RIR database for the space.200 of 673

Route objects not announced

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

168.0.36.0/23TCValid
2804:2ccc::/33TCValid
2804:2ccc::/34TCValid
2804:2ccc:2000::/35TCValid
2804:2ccc:4000::/34TCValid
2804:2ccc:4000::/35TCValid
2804:2ccc:6000::/35TCValid
2804:2ccc:8000::/33TCValid
2804:2ccc:8000::/34TCValid
2804:2ccc:8000::/35TCValid
2804:2ccc:a000::/35TCValid
2804:2ccc:c000::/34TCValid
2804:2ccc:c000::/35TCValid
2804:2ccc:e000::/35TCValid

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.