bgpreport

Network · data from 2026-11-12

AS270313 AS270313 - WN Tellecom

Registry name: AS270313 - WN Tellecom, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270313, 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.

177.10.72.0/23 No ROA Nonecovered by 177.10.72.0/22 2 0%low visibility 3
177.10.72.0/24 No ROA Nonecovered by 177.10.72.0/22 2 0%low visibility 3
177.10.73.0/24 No ROA Nonecovered by 177.10.72.0/22 2 0%low visibility 3
177.10.74.0/23 No ROA Nonecovered by 177.10.72.0/22 2 0%low visibility 3
177.10.74.0/24 No ROA Nonecovered by 177.10.72.0/22 2 0%low visibility 3
177.10.75.0/24 No ROA Nonecovered by 177.10.72.0/22 2 0%low visibility 3
177.10.72.0/22 No ROA Other IRR onlyRADB, TC 665 99% 67
2804:6a1c::/32 No ROA Other IRR onlyRADB, TC 636 100% 67

AS-SET

AS270313 isn't in PeeringDB, where networks name their 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none6
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none177.10.72.0/23No ROA covers it. Add a ROA for AS270313, maxLength 23.2 of 673
Route object: none177.10.72.0/23No route object for it. A route object for 177.10.72.0/22 with origin AS270313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270313 in the RIR database for the space.2 of 673
ROA: none177.10.72.0/24No ROA covers it. Add a ROA for AS270313, maxLength 24.2 of 673
Route object: none177.10.72.0/24No route object for it. A route object for 177.10.72.0/22 with origin AS270313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270313 in the RIR database for the space.2 of 673
ROA: none177.10.73.0/24No ROA covers it. Add a ROA for AS270313, maxLength 24.2 of 673
Route object: none177.10.73.0/24No route object for it. A route object for 177.10.72.0/22 with origin AS270313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270313 in the RIR database for the space.2 of 673
ROA: none177.10.74.0/23No ROA covers it. Add a ROA for AS270313, maxLength 23.2 of 673
Route object: none177.10.74.0/23No route object for it. A route object for 177.10.72.0/22 with origin AS270313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270313 in the RIR database for the space.2 of 673
ROA: none177.10.74.0/24No ROA covers it. Add a ROA for AS270313, maxLength 24.2 of 673
Route object: none177.10.74.0/24No route object for it. A route object for 177.10.72.0/22 with origin AS270313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270313 in the RIR database for the space.2 of 673
ROA: none177.10.75.0/24No ROA covers it. Add a ROA for AS270313, maxLength 24.2 of 673
Route object: none177.10.75.0/24No route object for it. A route object for 177.10.72.0/22 with origin AS270313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270313 in the RIR database for the space.2 of 673
ROA: none177.10.72.0/22No ROA covers it. Add a ROA for AS270313, maxLength 22.665 of 673
Route object: RIR177.10.72.0/22Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
ROA: none2804:6a1c::/32No ROA covers it. Add a ROA for AS270313, maxLength 32.636 of 636
Route object: RIR2804:6a1c::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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