bgpreport

Network · data from 2026-11-12

AS272581 SPEEDINFO TELECOM

Registry name: AS272581 - SPEEDINFO SOLUCOES INFORMATICA LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272581, 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:8578:4000::/34 Valid Nonecovered by 2804:8578::/33 634 100% 67
2804:8578:8000::/34 Valid Nonecovered by 2804:8578:8000::/33 634 100% 67
2804:8578:c000::/34 Valid Nonecovered by 2804:8578:8000::/33 634 100% 67
2804:8578::/34 Valid Nonecovered by 2804:8578::/33 1 0%low visibility 1
2804:8578::/43 Valid Nonecovered by 2804:8578::/33 1 0%low visibility 1
2804:8578:1::/48 Valid Nonecovered by 2804:8578::/33 1 0%low visibility 1
2804:8578:7::/48 Valid Nonecovered by 2804:8578::/33 1 0%low visibility 1
2804:8578:20::/43 Valid Nonecovered by 2804:8578::/33 1 0%low visibility 1
2804:8578:40::/43 Valid Nonecovered by 2804:8578::/33 1 0%low visibility 1
2804:8578:215::/48 Valid Nonecovered by 2804:8578::/33 1 0%low visibility 1
2804:8578:524::/48 Valid Nonecovered by 2804:8578::/33 1 0%low visibility 1
2804:8578:525::/48 Valid Nonecovered by 2804:8578::/33 1 0%low visibility 1
2804:8578:539::/48 Valid Nonecovered by 2804:8578::/33 1 0%low visibility 1
2804:8578:1201::/48 Valid Nonecovered by 2804:8578::/33 1 0%low visibility 1
2804:8578:2201::/48 Valid Nonecovered by 2804:8578::/33 1 0%low visibility 1
2804:8578:2214::/48 Valid Nonecovered by 2804:8578::/33 1 0%low visibility 1
191.160.40.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
191.160.40.0/24 Valid Other IRR onlyTC 672 100% 66
191.160.41.0/24 Valid Other IRR onlyTC 672 100% 66
2804:8578::/32 Valid Other IRR onlyRADB, TC 634 100% 69
2804:8578::/33 Valid Other IRR onlyRADB, TC 634 100% 69
2804:8578:8000::/33 Valid Other IRR onlyRADB, TC 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS272581: AS272581:AS-ROUTE. 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 (AS272581 isn't in the set, or no route object for AS272581 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 objectsAS272581 in itNot covered
AS272581:AS-ROUTE In no IRR database read today.

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

  • Route object: none16
  • Route object: RIR6
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: none2804:8578:4000::/34No route object for it. A route object for 2804:8578::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.634 of 636
Route object: none2804:8578:8000::/34No route object for it. A route object for 2804:8578:8000::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.634 of 636
Route object: none2804:8578:c000::/34No route object for it. A route object for 2804:8578:8000::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.634 of 636
Route object: none2804:8578::/34No route object for it. A route object for 2804:8578::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.1 of 636
Route object: none2804:8578::/43No route object for it. A route object for 2804:8578::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.1 of 636
Route object: none2804:8578:1::/48No route object for it. A route object for 2804:8578::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.1 of 636
Route object: none2804:8578:7::/48No route object for it. A route object for 2804:8578::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.1 of 636
Route object: none2804:8578:20::/43No route object for it. A route object for 2804:8578::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.1 of 636
Route object: none2804:8578:40::/43No route object for it. A route object for 2804:8578::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.1 of 636
Route object: none2804:8578:215::/48No route object for it. A route object for 2804:8578::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.1 of 636
Route object: none2804:8578:524::/48No route object for it. A route object for 2804:8578::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.1 of 636
Route object: none2804:8578:525::/48No route object for it. A route object for 2804:8578::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.1 of 636
Route object: none2804:8578:539::/48No route object for it. A route object for 2804:8578::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.1 of 636
Route object: none2804:8578:1201::/48No route object for it. A route object for 2804:8578::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.1 of 636
Route object: none2804:8578:2201::/48No route object for it. A route object for 2804:8578::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.1 of 636
Route object: none2804:8578:2214::/48No route object for it. A route object for 2804:8578::/33 with origin AS272581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272581 in the RIR database for the space.1 of 636
Route object: RIR191.160.40.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR191.160.40.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR191.160.41.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:8578::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:8578::/33Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:8578:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
AS-SET: not foundAS272581:AS-ROUTEPeeringDB names AS272581:AS-ROUTE; no IRR database read has it.

Route objects not announced

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