bgpreport

Network · data from 2026-11-12

AS268026 3L SERVICOS DE TECNOLOGIA

Registry name: AS268026 - UpNet Solutions, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268026, 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.
45.168.16.0/22 No ROA Other IRR onlyALTDB, RADB, TC 667 99% 66
45.168.16.0/23 No ROA Other IRR onlyALTDB, RADB, TC 666 99% 66
45.168.18.0/23 No ROA Other IRR onlyALTDB, RADB, TC 666 99% 66
2804:56d4::/32 No ROA Other IRR onlyALTDB, RADB, TC 631 99% 69
2804:56d4::/33 No ROA Other IRR onlyALTDB, RADB, TC 631 99% 69
2804:56d4:3::/48 No ROA Other IRR onlyRADB 631 99% 69
2804:56d4:6::/48 No ROA Other IRR onlyRADB 631 99% 69
2804:56d4:8000::/33 No ROA Other IRR onlyALTDB, RADB, TC 631 99% 69

AS-SET

AS268026'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 20 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none45.168.16.0/22No ROA covers it. Add a ROA for AS268026, maxLength 22.667 of 673
Route object: RIR45.168.16.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none45.168.16.0/23No ROA covers it. Add a ROA for AS268026, maxLength 23.666 of 673
Route object: RIR45.168.16.0/23Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none45.168.18.0/23No ROA covers it. Add a ROA for AS268026, maxLength 23.666 of 673
Route object: RIR45.168.18.0/23Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none2804:56d4::/32No ROA covers it. Add a ROA for AS268026, maxLength 32.631 of 636
Route object: RIR2804:56d4::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none2804:56d4::/33No ROA covers it. Add a ROA for AS268026, maxLength 33.631 of 636
Route object: RIR2804:56d4::/33Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none2804:56d4:3::/48No ROA covers it. Add a ROA for AS268026, maxLength 48.631 of 636
Route object: RIR2804:56d4:3::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:56d4:6::/48No ROA covers it. Add a ROA for AS268026, maxLength 48.631 of 636
Route object: RIR2804:56d4:6::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:56d4:8000::/33No ROA covers it. Add a ROA for AS268026, maxLength 33.631 of 636
Route object: RIR2804:56d4:8000::/33Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

45.168.16.0/24ALTDB, RADB, TCNo ROA
45.168.17.0/24ALTDB, RADB, TCNo ROA
45.168.18.0/24ALTDB, RADB, TCNo ROA
45.168.19.0/24ALTDB, RADB, TCNo 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.