bgpreport

Network · data from 2026-11-12

AS266448 XP Tecnologia

Registry name: AS266448 - GIGA MAIS FIBRA TELECOMUNICACOES S.A., BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266448, 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:37fc:2100::/40 Valid Nonecovered by 2804:37fc::/32 636 100% 67
170.82.220.0/22 Valid Other IRR onlyNTTCOM, RADB, TC 671 100% 67
2804:37fc::/32 Valid Other IRR onlyRADB, TC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS266448: RADB::AS-NIUFIBRA. 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 (AS266448 isn't in the set, or no route object for AS266448 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 objectsAS266448 in itNot covered
RADB::AS-NIUFIBRA 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 8 are in fix.csv.

  • Route object: none1
  • Route object: RIR2
  • AS-SET: not found1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2804:37fc:2100::/40No route object for it. A route object for 2804:37fc::/32 with origin AS266448 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266448 in the RIR database for the space.636 of 636
Route object: RIR170.82.220.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:37fc::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
AS-SET: not foundRADB::AS-NIUFIBRAPeeringDB names RADB::AS-NIUFIBRA; no IRR database read has it.

Route objects not announced

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

170.82.220.0/23RADBValid
170.82.220.0/24RADBValid
170.82.221.0/24RADBValid
170.82.222.0/24RADBValid

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.