bgpreport

Network · data from 2026-11-12

AS263939 Loginnet Telecom

Registry name: AS263939 - Loginnet Provedores Ltda ME, BR · PeeringDB

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

Announced routes

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

138.219.44.0/23 No ROA Nonecovered by 138.219.44.0/22 672 100% 66
138.219.46.0/23 No ROA Nonecovered by 138.219.44.0/22 672 100% 66
138.219.46.0/24 No ROA Nonecovered by 138.219.44.0/22 672 100% 66
138.219.47.0/24 No ROA Nonecovered by 138.219.44.0/22 672 100% 66
138.219.45.0/24 No ROA Nonecovered by 138.219.44.0/22 671 100% 66
2804:2814::/33 No ROA Nonecovered by 2804:2814::/32 635 100% 67
2804:2814::/40 No ROA Nonecovered by 2804:2814::/32 635 100% 67
2804:2814:8000::/33 No ROA Nonecovered by 2804:2814::/32 635 100% 67
138.219.44.1/32 No ROA Nonecovered by 138.219.44.0/24 4 1%low visibility 2
138.219.44.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
138.219.44.0/24 No ROA Other IRR onlyRADB 672 100% 66
2804:2814::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

AS263939'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.

  • ROA: none12
  • Route object: none9
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none138.219.44.0/23No ROA covers it. Add a ROA for AS263939, maxLength 23.672 of 673
Route object: none138.219.44.0/23No route object for it. A route object for 138.219.44.0/22 with origin AS263939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263939 in the RIR database for the space.672 of 673
ROA: none138.219.46.0/23No ROA covers it. Add a ROA for AS263939, maxLength 23.672 of 673
Route object: none138.219.46.0/23No route object for it. A route object for 138.219.44.0/22 with origin AS263939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263939 in the RIR database for the space.672 of 673
ROA: none138.219.46.0/24No ROA covers it. Add a ROA for AS263939, maxLength 24.672 of 673
Route object: none138.219.46.0/24No route object for it. A route object for 138.219.44.0/22 with origin AS263939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263939 in the RIR database for the space.672 of 673
ROA: none138.219.47.0/24No ROA covers it. Add a ROA for AS263939, maxLength 24.672 of 673
Route object: none138.219.47.0/24No route object for it. A route object for 138.219.44.0/22 with origin AS263939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263939 in the RIR database for the space.672 of 673
ROA: none138.219.45.0/24No ROA covers it. Add a ROA for AS263939, maxLength 24.671 of 673
Route object: none138.219.45.0/24No route object for it. A route object for 138.219.44.0/22 with origin AS263939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263939 in the RIR database for the space.671 of 673
ROA: none2804:2814::/33No ROA covers it. Add a ROA for AS263939, maxLength 33.635 of 636
Route object: none2804:2814::/33No route object for it. A route object for 2804:2814::/32 with origin AS263939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263939 in the RIR database for the space.635 of 636
ROA: none2804:2814::/40No ROA covers it. Add a ROA for AS263939, maxLength 40.635 of 636
Route object: none2804:2814::/40No route object for it. A route object for 2804:2814::/32 with origin AS263939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263939 in the RIR database for the space.635 of 636
ROA: none2804:2814:8000::/33No ROA covers it. Add a ROA for AS263939, maxLength 33.635 of 636
Route object: none2804:2814:8000::/33No route object for it. A route object for 2804:2814::/32 with origin AS263939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263939 in the RIR database for the space.635 of 636
ROA: none138.219.44.1/32No ROA covers it. Add a ROA for AS263939, maxLength 32.4 of 673
Route object: none138.219.44.1/32No route object for it. A route object for 138.219.44.0/24 with origin AS263939 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS263939 in the RIR database for the space.4 of 673
ROA: none138.219.44.0/22No ROA covers it. Add a ROA for AS263939, maxLength 22.672 of 673
Route object: RIR138.219.44.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none138.219.44.0/24No ROA covers it. Add a ROA for AS263939, maxLength 24.672 of 673
Route object: RIR138.219.44.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2804:2814::/32No ROA covers it. Add a ROA for AS263939, maxLength 32.634 of 636
Route object: RIR2804:2814::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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