bgpreport

Network · data from 2026-11-12

AS262393 TIG.com

Registry name: AS262393 - A ALVES GOMES INFORMATICA - ME, BR · PeeringDB

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

Announced routes

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

131.72.247.0/24 Valid Other IRR onlyALTDB, RADB, TC 671 100% 67
138.121.248.0/22 Valid Other IRR onlyALTDB, RADB, TC 671 100% 66
177.129.80.0/22 Valid Other IRR onlyALTDB, RADB, TC 671 100% 66
177.129.84.0/22 Valid Other IRR onlyALTDB, TC 671 100% 66
177.190.240.0/24 Valid Other IRR onlyALTDB, TC 671 100% 67
177.190.241.0/24 Valid Other IRR onlyALTDB, TC 671 100% 66
177.190.243.0/24 Valid Other IRR onlyALTDB, TC 671 100% 67
131.72.246.0/24 Valid Other IRR onlyALTDB, TC 670 100% 66
131.72.244.0/23 Valid Other IRR onlyALTDB, TC 668 99% 66
177.190.242.0/24 Valid Other IRR onlyALTDB, RADB, TC 668 99% 66
131.72.244.0/24 Valid Other IRR onlyALTDB, TC 667 99% 66
131.72.245.0/24 Valid Other IRR onlyALTDB, TC 667 99% 66
2804:8c8::/32 Valid Other IRR onlyALTDB, RADB, TC 632 99% 67
2804:8c8::/33 Valid Other IRR onlyALTDB, RADB, TC 331 52% 64
2804:8c8:8000::/33 Valid Other IRR onlyALTDB, TC 331 52% 64
138.121.248.0/23 Valid Other IRR onlyALTDB, TC 118 18% 43
138.121.250.0/23 Valid Other IRR onlyALTDB, TC 118 18% 43
177.129.80.0/24 Valid Other IRR onlyALTDB, TC 118 18% 43
177.129.87.0/24 Valid Other IRR onlyALTDB, TC 118 18% 43
2804:8c8::/35 Valid Other IRR onlyALTDB, TC 30 5%low visibility 11
2804:8c8:2000::/35 Valid Other IRR onlyALTDB, TC 30 5%low visibility 11
2804:8c8:4000::/35 Valid Other IRR onlyALTDB, TC 30 5%low visibility 11
2804:8c8:6000::/35 Valid Other IRR onlyALTDB, TC 30 5%low visibility 11
2804:8c8:8000::/35 Valid Other IRR onlyALTDB, TC 30 5%low visibility 11
2804:8c8:a000::/35 Valid Other IRR onlyALTDB, TC 30 5%low visibility 11
2804:8c8:c000::/35 Valid Other IRR onlyALTDB, TC 30 5%low visibility 11
2804:8c8:e000::/35 Valid Other IRR onlyALTDB, TC 30 5%low visibility 11

AS-SET

PeeringDB's irr_as_set for AS262393: AS-TIGCOM. 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 (AS262393 isn't in the set, or no route object for AS262393 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 objectsAS262393 in itNot covered
AS-TIGCOM ALTDB 61205 Yes 0
TC (also) 61205 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 37 are in fix.csv.

  • Route object: RIR27
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: RIR131.72.247.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.121.248.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.129.80.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.129.84.0/22Route object only in ALTDB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.190.240.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.190.241.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.190.243.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR131.72.246.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR131.72.244.0/23Route object only in ALTDB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR177.190.242.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR131.72.244.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR131.72.245.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:8c8::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:8c8::/33Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.331 of 636
Route object: RIR2804:8c8:8000::/33Route object only in ALTDB, TC. Add it in the RIR database for the space.331 of 636
Route object: RIR138.121.248.0/23Route object only in ALTDB, TC. Add it in the RIR database for the space.118 of 673
Route object: RIR138.121.250.0/23Route object only in ALTDB, TC. Add it in the RIR database for the space.118 of 673
Route object: RIR177.129.80.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.118 of 673
Route object: RIR177.129.87.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.118 of 673
Route object: RIR2804:8c8::/35Route object only in ALTDB, TC. Add it in the RIR database for the space.30 of 636
Route object: RIR2804:8c8:2000::/35Route object only in ALTDB, TC. Add it in the RIR database for the space.30 of 636
Route object: RIR2804:8c8:4000::/35Route object only in ALTDB, TC. Add it in the RIR database for the space.30 of 636
Route object: RIR2804:8c8:6000::/35Route object only in ALTDB, TC. Add it in the RIR database for the space.30 of 636
Route object: RIR2804:8c8:8000::/35Route object only in ALTDB, TC. Add it in the RIR database for the space.30 of 636
Route object: RIR2804:8c8:a000::/35Route object only in ALTDB, TC. Add it in the RIR database for the space.30 of 636
Route object: RIR2804:8c8:c000::/35Route object only in ALTDB, TC. Add it in the RIR database for the space.30 of 636
Route object: RIR2804:8c8:e000::/35Route object only in ALTDB, TC. Add it in the RIR database for the space.30 of 636

Route objects not announced

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

131.72.244.0/22ALTDB, RADB, TCNo ROA
131.72.246.0/23ALTDB, TCNo ROA
138.121.248.0/24ALTDB, TCValid
138.121.249.0/24ALTDB, TCValid
138.121.250.0/24ALTDB, TCValid
138.121.251.0/24ALTDB, TCValid
177.129.80.0/21ALTDB, TCNo ROA
177.190.240.0/22ALTDB, RADB, TCNo ROA
177.190.240.0/23ALTDB, RADB, TCNo ROA
177.190.242.0/23ALTDB, TCNo ROA

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.