bgpreport

Network · data from 2026-11-12

AS274481 SAGE LINK PROVEDOR DE INTERNET LTDA

Registry name: AS274481 - SAGE LINK PROVEDOR DE INTERNET LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274481, 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:94d4:140::/43 Valid Nonecovered by 2804:94d4::/36 634 100% 67
2804:94d4:a000::/36 Valid Nonecovered by 2804:94d4::/32 634 100% 67
2804:94d4::/32 Valid Other IRR onlyTC 635 100% 67
2804:94d4:1000::/36 Valid Other IRR onlyTC 634 100% 67
2804:94d4:4000::/36 Valid Other IRR onlyTC 634 100% 67
2804:94d4:8000::/36 Valid Other IRR onlyTC 634 100% 67
2804:94d4:c000::/36 Valid Other IRR onlyTC 634 100% 67
2804:94d4::/36 Valid Other IRR onlyTC 633 100% 67

AS-SET

AS274481'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 8 are in fix.csv.

  • Route object: none2
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: none2804:94d4:140::/43No route object for it. A route object for 2804:94d4::/36 with origin AS274481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274481 in the RIR database for the space.634 of 636
Route object: none2804:94d4:a000::/36No route object for it. A route object for 2804:94d4::/32 with origin AS274481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274481 in the RIR database for the space.634 of 636
Route object: RIR2804:94d4::/32Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:94d4:1000::/36Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:94d4:4000::/36Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:94d4:8000::/36Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:94d4:c000::/36Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:94d4::/36Route object only in TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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