bgpreport

Network · data from 2026-11-12

AS263941 MegaNET Serviços de Comunicação Multimídia

Registry name: AS263941 - MegaNET Servicos de Comunicacao Multimidia Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263941, 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.100.0/22 No ROA Other IRR onlyNTTCOM, RADB, TC 668 99% 66
138.219.100.0/24 No ROA Other IRR onlyRADB 667 99% 67
138.219.101.0/24 No ROA Other IRR onlyRADB 667 99% 67
138.219.103.0/24 No ROA Other IRR onlyRADB 667 99% 67
138.219.102.0/24 No ROA Other IRR onlyRADB 666 99% 67
2804:281c::/32 No ROA Other IRR onlyNTTCOM, RADB, TC 632 99% 67
2804:5330:602::/48 No ROA Other IRR onlyRADB 365 57% 65
206.84.203.0/24 Valid Nonecovered by 206.84.202.0/23 667 99% 66
206.84.202.0/24 Valid Other IRR onlyRADB 226 34% 57

AS-SET

AS263941'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 19 are in fix.csv.

  • ROA: none7
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none138.219.100.0/22No ROA covers it. Add a ROA for AS263941, maxLength 22.668 of 673
Route object: RIR138.219.100.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none138.219.100.0/24No ROA covers it. Add a ROA for AS263941, maxLength 24.667 of 673
Route object: RIR138.219.100.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none138.219.101.0/24No ROA covers it. Add a ROA for AS263941, maxLength 24.667 of 673
Route object: RIR138.219.101.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none138.219.103.0/24No ROA covers it. Add a ROA for AS263941, maxLength 24.667 of 673
Route object: RIR138.219.103.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none138.219.102.0/24No ROA covers it. Add a ROA for AS263941, maxLength 24.666 of 673
Route object: RIR138.219.102.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none2804:281c::/32No ROA covers it. Add a ROA for AS263941, maxLength 32.632 of 636
Route object: RIR2804:281c::/32Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.632 of 636
ROA: none2804:5330:602::/48No ROA covers it. Add a ROA for AS263941, maxLength 48.365 of 636
Route object: RIR2804:5330:602::/48Route object only in RADB. Add it in the RIR database for the space.365 of 636
Route object: none206.84.203.0/24No route object for it. A route object for 206.84.202.0/23 with origin AS263941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263941 in the RIR database for the space.667 of 673
Route object: RIR206.84.202.0/24Route object only in RADB. Add it in the RIR database for the space.226 of 673

Route objects not announced

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

38.219.100.0/22RADBNo ROA
164.163.228.0/22RADBNo ROA
206.84.202.0/23ARINValid

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.