bgpreport

Network · data from 2026-11-12

AS267978 AS267978 - JOTA NET TELECOMUNICACOES LTDA - ME

Registry name: AS267978 - JOTA NET TELECOMUNICACOES LTDA - ME, BR · not in PeeringDB

5IPv4 routes 20.0% RPKI valid · 60.0% with a route object
7IPv6 routes 0.0% RPKI valid · 14.3% with a route object
3RPKI invalid 3 origin · 0 maxLength
8No ROA 8 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS267978, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267978, 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:7560:2c0::/45 Invalid: origin None 47 7%low visibility 26
2804:7560:2c8::/45 Invalid: origin None 47 7%low visibility 26
2804:7560:2ca::/47 Invalid: origin None 47 7%low visibility 26
45.166.158.0/24 No ROA Nonecovered by 45.166.156.0/22 672 100% 66
45.166.157.0/24 No ROA Nonecovered by 45.166.156.0/22 668 99% 67
2804:5620:100::/48 No ROA Nonecovered by 2804:5620::/32 632 99% 67
2804:5620:100:2000::/51 No ROA Nonecovered by 2804:5620::/32 2 0%low visibility 2
2804:5620:100:4000::/51 No ROA Nonecovered by 2804:5620::/32 2 0%low visibility 2
45.166.159.0/24 No ROA Other IRR onlyRADB 671 100% 67
45.166.156.0/24 No ROA Other IRR onlyRADB 668 99% 66
2804:5620:2::/48 No ROA Other IRR onlyRADB 634 100% 67
151.247.144.0/24 Valid RIR databaseRADB, RIPE 666 99% 67

AS-SET

AS267978 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 25 are in fix.csv.

  • ROA: origin3
  • ROA: none8
  • Route object: none8
  • Route object: RIR3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin2804:7560:2c0::/45ROAs covering it name AS271042, not AS267978. If AS267978 should announce it, add a ROA for AS267978.47 of 636
Route object: none2804:7560:2c0::/45No route object for it. Add a route object with origin AS267978 in the RIR database for the space.47 of 636
ROA: origin2804:7560:2c8::/45ROAs covering it name AS271042, not AS267978. If AS267978 should announce it, add a ROA for AS267978.47 of 636
Route object: none2804:7560:2c8::/45No route object for it. Add a route object with origin AS267978 in the RIR database for the space.47 of 636
ROA: origin2804:7560:2ca::/47ROAs covering it name AS271042, not AS267978. If AS267978 should announce it, add a ROA for AS267978.47 of 636
Route object: none2804:7560:2ca::/47No route object for it. Add a route object with origin AS267978 in the RIR database for the space.47 of 636
ROA: none45.166.158.0/24No ROA covers it. Add a ROA for AS267978, maxLength 24.672 of 673
Route object: none45.166.158.0/24No route object for it. A route object for 45.166.156.0/22 with origin AS267978 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267978 in the RIR database for the space.672 of 673
ROA: none45.166.157.0/24No ROA covers it. Add a ROA for AS267978, maxLength 24.668 of 673
Route object: none45.166.157.0/24No route object for it. A route object for 45.166.156.0/22 with origin AS267978 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267978 in the RIR database for the space.668 of 673
ROA: none2804:5620:100::/48No ROA covers it. Add a ROA for AS267978, maxLength 48.632 of 636
Route object: none2804:5620:100::/48No route object for it. A route object for 2804:5620::/32 with origin AS267978 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267978 in the RIR database for the space.632 of 636
ROA: none2804:5620:100:2000::/51No ROA covers it. Add a ROA for AS267978, maxLength 51.2 of 636
Route object: none2804:5620:100:2000::/51No route object for it. A route object for 2804:5620::/32 with origin AS267978 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS267978 in the RIR database for the space.2 of 636
ROA: none2804:5620:100:4000::/51No ROA covers it. Add a ROA for AS267978, maxLength 51.2 of 636
Route object: none2804:5620:100:4000::/51No route object for it. A route object for 2804:5620::/32 with origin AS267978 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS267978 in the RIR database for the space.2 of 636
ROA: none45.166.159.0/24No ROA covers it. Add a ROA for AS267978, maxLength 24.671 of 673
Route object: RIR45.166.159.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.166.156.0/24No ROA covers it. Add a ROA for AS267978, maxLength 24.668 of 673
Route object: RIR45.166.156.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:5620:2::/48No ROA covers it. Add a ROA for AS267978, maxLength 48.634 of 636
Route object: RIR2804:5620:2::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

45.166.156.0/22RADBNo ROA
2804:5620::/32RADBNo ROA
2804:5620:210::/48RADBNo 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.