bgpreport

Network · data from 2026-11-12

AS270743 GLNet Rincão

Registry name: AS270743 - G L DE BARROS E CIA LTDA ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270743, 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:70d8:c::/46 No ROA Nonecovered by 2804:70d8::/32 355 56% 65
187.102.198.0/24 No ROA Nonecovered by 187.102.198.0/23 210 31% 56
187.102.199.0/24 No ROA Nonecovered by 187.102.198.0/23 210 31% 56
187.102.198.0/23 No ROA Other IRR onlyTC 669 99% 67
2804:70d8::/32 No ROA Other IRR onlyTC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS270743: TC::AS270743. 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 (AS270743 isn't in the set, or no route object for AS270743 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 objectsAS270743 in itNot covered
TC::AS270743 A single AS number, not a set: AS270743 (this network), 2 route objects.

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

  • ROA: none5
  • Route object: none3
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none2804:70d8:c::/46No ROA covers it. Add a ROA for AS270743, maxLength 46.355 of 636
Route object: none2804:70d8:c::/46No route object for it. A route object for 2804:70d8::/32 with origin AS270743 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270743 in the RIR database for the space.355 of 636
ROA: none187.102.198.0/24No ROA covers it. Add a ROA for AS270743, maxLength 24.210 of 673
Route object: none187.102.198.0/24No route object for it. A route object for 187.102.198.0/23 with origin AS270743 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270743 in the RIR database for the space.210 of 673
ROA: none187.102.199.0/24No ROA covers it. Add a ROA for AS270743, maxLength 24.210 of 673
Route object: none187.102.199.0/24No route object for it. A route object for 187.102.198.0/23 with origin AS270743 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270743 in the RIR database for the space.210 of 673
ROA: none187.102.198.0/23No ROA covers it. Add a ROA for AS270743, maxLength 23.669 of 673
Route object: RIR187.102.198.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:70d8::/32No ROA covers it. Add a ROA for AS270743, maxLength 32.634 of 636
Route object: RIR2804:70d8::/32Route object only in TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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