bgpreport

Network · data from 2026-11-12

AS267369 ADENILTON DA PAIXO RIBEIRO

Registry name: AS267369 - MAFREDINE TELECOMUNICACOES EIRELI, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267369, 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.
45.234.176.0/23 No ROA Other origin onlycovered by 45.234.176.0/22 669 99% 67
45.234.176.0/22 No ROA Other IRR onlyNTTCOM, RADB, TC 672 100% 67
45.234.178.0/23 No ROA Other IRR onlyRADB 672 100% 67
45.234.177.0/24 No ROA Other IRR onlyRADB 671 100% 67
2804:4c68::/32 No ROA Other IRR onlyNTTCOM, RADB, TC 636 100% 67

AS-SET

AS267369'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 12 are in fix.csv.

  • ROA: none5
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.234.176.0/23No ROA covers it. Add a ROA for AS267369, maxLength 23.669 of 673
Route object: none45.234.176.0/23Route objects for it name AS52873. A route object for 45.234.176.0/22 with origin AS267369 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267369 in the RIR database for the space.669 of 673
ROA: none45.234.176.0/22No ROA covers it. Add a ROA for AS267369, maxLength 22.672 of 673
Route object: RIR45.234.176.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.234.178.0/23No ROA covers it. Add a ROA for AS267369, maxLength 23.672 of 673
Route object: RIR45.234.178.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.234.177.0/24No ROA covers it. Add a ROA for AS267369, maxLength 24.671 of 673
Route object: RIR45.234.177.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:4c68::/32No ROA covers it. Add a ROA for AS267369, maxLength 32.636 of 636
Route object: RIR2804:4c68::/32Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

45.234.178.0/24RADBNo ROA
45.234.179.0/24RADBNo ROA

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.