bgpreport

Network · data from 2026-11-12

AS273564 SNET TELECOM LTDA

Registry name: AS273564 - SNET TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273564, 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:90a0:8000::/33 Invalid: maxLength Nonecovered by 2804:90a0::/32 1 0%low visibility 1
2804:90a0:8300::/40 Valid Nonecovered by 2804:90a0::/32 631 99% 67
2804:90a0:8400::/48 Valid Nonecovered by 2804:90a0::/32 631 99% 67
2804:90a0:8200::/39 Valid Nonecovered by 2804:90a0::/32 630 99% 67
2804:90a0:8200::/40 Valid Nonecovered by 2804:90a0::/32 626 98% 67
2804:90a0::/33 Valid Other IRR onlyTC 636 100% 67
2804:90a0:6300::/40 Valid Other IRR onlyTC 636 100% 67
2804:90a0:7f00::/40 Valid Other IRR onlyTC 636 100% 67
2804:90a0::/32 Valid Other IRR onlyRADB, TC 1 0%low visibility 1

AS-SET

AS273564'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 10 are in fix.csv.

  • ROA: maxLength1
  • Route object: none5
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:90a0:8000::/33ROA 2804:90a0::/32 AS273564 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:90a0:8000::/33.1 of 636
Route object: none2804:90a0:8000::/33No route object for it. A route object for 2804:90a0::/32 with origin AS273564 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273564 in the RIR database for the space.1 of 636
Route object: none2804:90a0:8300::/40No route object for it. A route object for 2804:90a0::/32 with origin AS273564 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273564 in the RIR database for the space.631 of 636
Route object: none2804:90a0:8400::/48No route object for it. A route object for 2804:90a0::/32 with origin AS273564 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273564 in the RIR database for the space.631 of 636
Route object: none2804:90a0:8200::/39No route object for it. A route object for 2804:90a0::/32 with origin AS273564 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273564 in the RIR database for the space.630 of 636
Route object: none2804:90a0:8200::/40No route object for it. A route object for 2804:90a0::/32 with origin AS273564 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273564 in the RIR database for the space.626 of 636
Route object: RIR2804:90a0::/33Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:90a0:6300::/40Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:90a0:7f00::/40Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:90a0::/32Route object only in RADB, TC. Add it in the RIR database for the space.1 of 636

Route objects not announced

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