bgpreport

Network · data from 2026-11-12

AS269450 AS269450 - MOTA TELECOM LTDA

Registry name: AS269450 - MOTA TELECOM LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269450, 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:64d0::/35 Valid Nonecovered by 2804:64d0::/32 635 100% 67
2804:64d0::/36 Valid Nonecovered by 2804:64d0::/32 635 100% 67
2804:64d0:1000::/36 Valid Nonecovered by 2804:64d0::/32 635 100% 67
45.187.28.0/22 Valid Other IRR onlyALTDB, RADB, TC 669 99% 67
45.187.28.0/23 Valid Other IRR onlyALTDB 667 99% 67
45.187.28.0/24 Valid Other IRR onlyALTDB, RADB 667 99% 67
45.187.29.0/24 Valid Other IRR onlyALTDB, RADB 667 99% 67
45.187.30.0/23 Valid Other IRR onlyALTDB 666 99% 67
45.187.30.0/24 Valid Other IRR onlyALTDB, RADB 666 99% 67
45.187.31.0/24 Valid Other IRR onlyALTDB, RADB 666 99% 67
2804:64d0::/32 Valid Other IRR onlyALTDB, RADB, TC 634 100% 67

AS-SET

AS269450 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 11 are in fix.csv.

  • Route object: none3
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
Route object: none2804:64d0::/35No route object for it. A route object for 2804:64d0::/32 with origin AS269450 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269450 in the RIR database for the space.635 of 636
Route object: none2804:64d0::/36No route object for it. A route object for 2804:64d0::/32 with origin AS269450 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269450 in the RIR database for the space.635 of 636
Route object: none2804:64d0:1000::/36No route object for it. A route object for 2804:64d0::/32 with origin AS269450 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269450 in the RIR database for the space.635 of 636
Route object: RIR45.187.28.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.187.28.0/23Route object only in ALTDB. Add it in the RIR database for the space.667 of 673
Route object: RIR45.187.28.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR45.187.29.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR45.187.30.0/23Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
Route object: RIR45.187.30.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR45.187.31.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:64d0::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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