bgpreport

Network · data from 2026-11-12

AS266454 EXPAND TV

Registry name: AS266454 - EXPAND TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266454, 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:3814::/34 Valid Nonecovered by 2804:3814::/32 113 18% 43
2804:3814:4000::/34 Valid Nonecovered by 2804:3814::/32 113 18% 43
2804:3814:8000::/34 Valid Nonecovered by 2804:3814::/32 113 18% 43
2804:3814:c000::/34 Valid Nonecovered by 2804:3814::/32 113 18% 43
2804:3814::/33 Valid Nonecovered by 2804:3814::/32 2 0%low visibility 2
2804:3814:8000::/33 Valid Nonecovered by 2804:3814::/32 2 0%low visibility 2
170.83.0.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
179.0.124.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
2804:3814::/32 Valid Other IRR onlyRADB 631 99% 67
170.83.0.0/24 Valid Other IRR onlyRADB 127 19% 44
170.83.2.0/24 Valid Other IRR onlyRADB 127 19% 44
170.83.3.0/24 Valid Other IRR onlyRADB 127 19% 44
179.0.124.0/24 Valid Other IRR onlyRADB 127 19% 44
179.0.125.0/24 Valid Other IRR onlyRADB 127 19% 44
179.0.126.0/24 Valid Other IRR onlyRADB 127 19% 44
179.0.127.0/24 Valid Other IRR onlyRADB 127 19% 44
170.83.1.0/24 Valid Other IRR onlyRADB 126 19% 44

AS-SET

PeeringDB's irr_as_set for AS266454: AS-EXPAND. 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 (AS266454 isn't in the set, or no route object for AS266454 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 objectsAS266454 in itNot covered
AS-EXPAND TC 2123 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 21 are in fix.csv.

  • Route object: none6
  • Route object: RIR11
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2804:3814::/34No route object for it. A route object for 2804:3814::/32 with origin AS266454 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266454 in the RIR database for the space.113 of 636
Route object: none2804:3814:4000::/34No route object for it. A route object for 2804:3814::/32 with origin AS266454 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266454 in the RIR database for the space.113 of 636
Route object: none2804:3814:8000::/34No route object for it. A route object for 2804:3814::/32 with origin AS266454 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266454 in the RIR database for the space.113 of 636
Route object: none2804:3814:c000::/34No route object for it. A route object for 2804:3814::/32 with origin AS266454 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266454 in the RIR database for the space.113 of 636
Route object: none2804:3814::/33No route object for it. A route object for 2804:3814::/32 with origin AS266454 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266454 in the RIR database for the space.2 of 636
Route object: none2804:3814:8000::/33No route object for it. A route object for 2804:3814::/32 with origin AS266454 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266454 in the RIR database for the space.2 of 636
Route object: RIR170.83.0.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR179.0.124.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:3814::/32Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR170.83.0.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR170.83.2.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR170.83.3.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR179.0.124.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR179.0.125.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR179.0.126.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR179.0.127.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR170.83.1.0/24Route object only in RADB. Add it in the RIR database for the space.126 of 673

Route objects not announced

Route objects with origin AS266454 whose prefix no peer sees AS266454 announce. Many are kept on purpose (backup routes, space announced only in some places).

170.83.0.0/23RADBValid
170.83.2.0/23RADBValid
179.0.124.0/23RADBValid
179.0.126.0/23RADBValid

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.