bgpreport

Network · data from 2026-11-12

AS267429 GRAFNET TELECOM

Registry name: AS267429 - GRAFNET TELECOM, BR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
7IPv6 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
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS267429, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267429, 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.
181.191.168.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
181.191.171.0/24 Valid Other IRR onlyRADB, TC 667 99% 66
2804:4160::/32 Valid Other IRR onlyRADB, TC 632 99% 67
2804:4160::/33 Valid Other IRR onlyTC 336 53% 65
2804:4160::/34 Valid Other IRR onlyTC 336 53% 65
2804:4160:4000::/34 Valid Other IRR onlyTC 336 53% 65
2804:4160:8000::/33 Valid Other IRR onlyTC 336 53% 65
2804:4160:8000::/34 Valid Other IRR onlyTC 336 53% 65
2804:4160:c000::/34 Valid Other IRR onlyTC 336 53% 65
181.191.168.0/23 Valid Other IRR onlyRADB, TC 135 20% 45
181.191.170.0/23 Valid Other IRR onlyRADB, TC 132 20% 44

AS-SET

PeeringDB's irr_as_set for AS267429: AS267429:AS-ALL. 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 (AS267429 isn't in the set, or no route object for AS267429 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 objectsAS267429 in itNot covered
AS267429:AS-ALL TC 1313164 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 11 are in fix.csv.

  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
Route object: RIR181.191.168.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR181.191.171.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:4160::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:4160::/33Route object only in TC. Add it in the RIR database for the space.336 of 636
Route object: RIR2804:4160::/34Route object only in TC. Add it in the RIR database for the space.336 of 636
Route object: RIR2804:4160:4000::/34Route object only in TC. Add it in the RIR database for the space.336 of 636
Route object: RIR2804:4160:8000::/33Route object only in TC. Add it in the RIR database for the space.336 of 636
Route object: RIR2804:4160:8000::/34Route object only in TC. Add it in the RIR database for the space.336 of 636
Route object: RIR2804:4160:c000::/34Route object only in TC. Add it in the RIR database for the space.336 of 636
Route object: RIR181.191.168.0/23Route object only in RADB, TC. Add it in the RIR database for the space.135 of 673
Route object: RIR181.191.170.0/23Route object only in RADB, TC. Add it in the RIR database for the space.132 of 673

Route objects not announced

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