bgpreport

Network · data from 2026-11-12

AS274689 SuperMaisLink

Registry name: AS274689 - ISP SERVICOS DE INTERNET LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274689, 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:9218:4000::/34 No ROA Nonecovered by 2804:9218::/33 629 99% 67
2804:9218::/34 No ROA Nonecovered by 2804:9218::/33 351 55% 64
2804:9218:8000::/34 No ROA Nonecovered by 2804:9218:8000::/33 351 55% 64
2804:9218:c000::/34 No ROA Nonecovered by 2804:9218:8000::/33 351 55% 64
191.242.36.0/23 No ROA Other IRR onlyTC 672 100% 66
191.242.38.0/23 No ROA Other IRR onlyTC 672 100% 66
191.242.36.0/22 No ROA Other IRR onlyTC 669 99% 66
2804:9218::/32 No ROA Other IRR onlyTC 630 99% 67
2804:9218::/33 No ROA Other IRR onlyTC 630 99% 67
2804:9218:8000::/33 No ROA Other IRR onlyTC 630 99% 67
191.242.36.0/24 No ROA Other IRR onlyTC 201 30% 54
191.242.38.0/24 No ROA Other IRR onlyTC 201 30% 54
191.242.39.0/24 No ROA Other IRR onlyTC 201 30% 54
191.242.37.0/24 No ROA Other IRR onlyTC 200 30% 54

AS-SET

PeeringDB's irr_as_set for AS274689: AS274689:AS-ISPGROUP-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS274689 isn't in the set, or no route object for AS274689 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS274689 in itNot covered
AS274689:AS-ISPGROUP-ALL TC 1310 Yes 0

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 28 are in fix.csv.

  • ROA: none14
  • Route object: none4
  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
ROA: none2804:9218:4000::/34No ROA covers it. Add a ROA for AS274689, maxLength 34.629 of 636
Route object: none2804:9218:4000::/34No route object for it. A route object for 2804:9218::/33 with origin AS274689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274689 in the RIR database for the space.629 of 636
ROA: none2804:9218::/34No ROA covers it. Add a ROA for AS274689, maxLength 34.351 of 636
Route object: none2804:9218::/34No route object for it. A route object for 2804:9218::/33 with origin AS274689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274689 in the RIR database for the space.351 of 636
ROA: none2804:9218:8000::/34No ROA covers it. Add a ROA for AS274689, maxLength 34.351 of 636
Route object: none2804:9218:8000::/34No route object for it. A route object for 2804:9218:8000::/33 with origin AS274689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274689 in the RIR database for the space.351 of 636
ROA: none2804:9218:c000::/34No ROA covers it. Add a ROA for AS274689, maxLength 34.351 of 636
Route object: none2804:9218:c000::/34No route object for it. A route object for 2804:9218:8000::/33 with origin AS274689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274689 in the RIR database for the space.351 of 636
ROA: none191.242.36.0/23No ROA covers it. Add a ROA for AS274689, maxLength 23.672 of 673
Route object: RIR191.242.36.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none191.242.38.0/23No ROA covers it. Add a ROA for AS274689, maxLength 23.672 of 673
Route object: RIR191.242.38.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none191.242.36.0/22No ROA covers it. Add a ROA for AS274689, maxLength 22.669 of 673
Route object: RIR191.242.36.0/22Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:9218::/32No ROA covers it. Add a ROA for AS274689, maxLength 32.630 of 636
Route object: RIR2804:9218::/32Route object only in TC. Add it in the RIR database for the space.630 of 636
ROA: none2804:9218::/33No ROA covers it. Add a ROA for AS274689, maxLength 33.630 of 636
Route object: RIR2804:9218::/33Route object only in TC. Add it in the RIR database for the space.630 of 636
ROA: none2804:9218:8000::/33No ROA covers it. Add a ROA for AS274689, maxLength 33.630 of 636
Route object: RIR2804:9218:8000::/33Route object only in TC. Add it in the RIR database for the space.630 of 636
ROA: none191.242.36.0/24No ROA covers it. Add a ROA for AS274689, maxLength 24.201 of 673
Route object: RIR191.242.36.0/24Route object only in TC. Add it in the RIR database for the space.201 of 673
ROA: none191.242.38.0/24No ROA covers it. Add a ROA for AS274689, maxLength 24.201 of 673
Route object: RIR191.242.38.0/24Route object only in TC. Add it in the RIR database for the space.201 of 673
ROA: none191.242.39.0/24No ROA covers it. Add a ROA for AS274689, maxLength 24.201 of 673
Route object: RIR191.242.39.0/24Route object only in TC. Add it in the RIR database for the space.201 of 673
ROA: none191.242.37.0/24No ROA covers it. Add a ROA for AS274689, maxLength 24.200 of 673
Route object: RIR191.242.37.0/24Route object only in TC. Add it in the RIR database for the space.200 of 673

Route objects not announced

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