bgpreport

Network · data from 2026-11-12

AS275798 ASN275798

Registry name: AS275798 - Universidade Federal de Santa Catarina, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS275798, 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:1f80::/33 Valid Nonecovered by 2804:1f80::/32 15 2%low visibility 8
2804:1f80:8000::/33 Valid Nonecovered by 2804:1f80::/32 15 2%low visibility 8
2804:1f80::/32 Valid Other IRR onlyTC 632 99% 67

AS-SET

AS275798'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 3 are in fix.csv.

  • Route object: none2
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: none2804:1f80::/33No route object for it. A route object for 2804:1f80::/32 with origin AS275798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275798 in the RIR database for the space.15 of 636
Route object: none2804:1f80:8000::/33No route object for it. A route object for 2804:1f80::/32 with origin AS275798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275798 in the RIR database for the space.15 of 636
Route object: RIR2804:1f80::/32Route object only in TC. Add it in the RIR database for the space.632 of 636

Route objects not announced

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