bgpreport

Network · data from 2026-11-12

AS264221 phase projetos e serviços de engenharia

Registry name: AS264221 - ONLINE NORTE TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264221, 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.117.36.158/32 Invalid: maxLength Nonecovered by 138.117.36.0/24 3 0%low visibility 3
192.141.216.0/22 Valid Other IRR onlyRADB 670 100% 66
45.185.156.0/22 Valid Other IRR onlyRADB 669 99% 66
138.117.36.0/22 Valid Other IRR onlyRADB, TC 669 99% 66
138.117.36.0/23 Valid Other IRR onlyRADB 669 99% 66
138.117.38.0/23 Valid Other IRR onlyRADB 669 99% 66
192.141.216.0/23 Valid Other IRR onlyRADB 668 99% 66
192.141.218.0/23 Valid Other IRR onlyRADB 667 99% 66
2804:2468::/32 Valid Other IRR onlyRADB, TC 635 100% 67
45.185.158.0/23 Valid Other IRR onlyRADB 68 10% 32
45.185.156.0/23 Valid Other IRR onlyRADB 65 10%low visibility 31

AS-SET

AS264221'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 54 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR10
  • Route object: not announced42
ChangePrefix or setDetailFull-table peers
ROA: maxLength138.117.36.158/32ROA 138.117.36.0/22 AS264221 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 138.117.36.158/32.3 of 673
Route object: none138.117.36.158/32No route object for it. A route object for 138.117.36.0/24 with origin AS264221 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS264221 in the RIR database for the space.3 of 673
Route object: RIR192.141.216.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.185.156.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR138.117.36.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR138.117.36.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR138.117.38.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR192.141.216.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR192.141.218.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:2468::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR45.185.158.0/23Route object only in RADB. Add it in the RIR database for the space.68 of 673
Route object: RIR45.185.156.0/23Route object only in RADB. Add it in the RIR database for the space.65 of 673

Route objects not announced

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

138.117.36.0/24RADBValid
138.117.37.0/24RADBValid
138.117.38.0/24RADBValid
138.117.39.0/24RADBValid
2804:2468::/33RADBValid
2804:2468:1::/48RADBValid
2804:2468:80f::/48RADBValid
2804:2468:882::/48RADBValid
2804:2468:884::/48RADBValid
2804:2468:888::/48RADBValid
2804:2468:88f::/48RADBValid
2804:2468:3404::/48RADBValid
2804:2468:3408::/48RADBValid
2804:2468:340c::/48RADBValid
2804:2468:3440::/44RADBValid
2804:2468:3480::/44RADBValid
2804:2468:34c0::/44RADBValid
2804:2468:3880::/48RADBValid
2804:2468:408f::/48RADBValid
2804:2468:40c0::/48RADBValid
2804:2468:4200::/40RADBValid
2804:2468:4800::/40RADBValid
2804:2468:4a00::/40RADBValid
2804:2468:8000::/33RADBValid
2804:2468:a08c::/48RADBValid
2804:2468:a08d::/48RADBValid
2804:2468:a08e::/48RADBValid
2804:2468:a08f::/48RADBValid
2804:2468:a880::/48RADBValid
2804:2468:a888::/48RADBValid
2804:2468:c011::/48RADBValid
2804:2468:c480::/48RADBValid
2804:2468:c488::/48RADBValid
2804:2468:c880::/48RADBValid
2804:2468:c881::/48RADBValid
2804:2468:c888::/48RADBValid
2804:2468:cc40::/48RADBValid
2804:2468:e080::/48RADBValid
2804:2468:e280::/48RADBValid
2804:2468:ec80::/48RADBValid
2804:2468:f300::/48RADBValid
2804:2468:f301::/48RADBValid

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.